janssen@parc.xerox.com (Bill Janssen) (08/22/90)
I notice that in atk/typescript/fcomp.c, the code for command completion is #ifdef'ed out. Any particular reason for this? Bill
dba+@ANDREW.CMU.EDU (David Anderson) (08/22/90)
Excerpts from internet.info-andrew: 21-Aug-90 command completion in types.. Bill Janssen@parc.xerox. (130+0) > I notice that in atk/typescript/fcomp.c, the code for command completion > is #ifdef'ed out. Any particular reason for this? Well, the code works (or at least did), but seemed pretty useless as is. The problem with it was that there were too many times I wanted to use it, but the typescript only had the text around for the last couple of commands -- this could be fixed easily enough by saving the commands separately (outside the typescript's text object) -- so I left the code there, but #ifdef'ed out. It might be interesting to fix this, and then bind it to esc-=. (The way this should work is you type a little bit, hit escape-equals, and fcomp completes with the text of the most recent typescript command starting with that bit of text. Repeated use of esc-= brings up previous matches. The empty string matches all the commands (as a prefix), so there's reasonable backwards compatibility.) --david [An Andrew ToolKit view (a spreadsheet) was included here, but could not be displayed.]