On Thu, Oct 11, 2001 at 12:10:13PM -0700, Brian Weiss wrote: >On Mon, Oct 08, 2001 at 06:27:27PM +0700, qMax wrote: >> To make it possible to find matching commands and variables >> i had to grep sources and list all possible matches in script. >> To make it correctly determine type of command arg >> (egg after /window) i have to examine all sources >> and list command syntax in script. >> >> Is there better solution ? >> Is it possible ?
>I was unable to find the specified script on your site, so I can't >comment on your code. I'm also not exactly sure what you're trying to >do here, but let's see if this hits the nail on the head... Sorry, it is at ftp://ftp.civo.aca.nsc.ru/userq/qmax/softines/epic4-scripts/completion.irc >Are you trying to implement command/variable completion? If so there are >some very useful builtin commands/functions you should know about. >Command completion in EPIC is accomplished via the internal function >command_completion. You can access this function via the /parsekey command. command_completion just lists all comands and aliases and I havent find any way to grab this output to sequentialy substitute into input line. >If you want to look at my latest tabkey script you can find it packaged with I'll see... -- qMax _______________________________________________ List mailing list [EMAIL PROTECTED] http://epicsol.org/mailman/listinfo/list
