Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Thinking about Functions/Completion/* differently

X-seq: zsh-workers 5391
From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
To: zsh-workers@xxxxxxxxxxxxxx
Subject: Re: Thinking about Functions/Completion/* differently
Date: Mon, 15 Feb 1999 14:12:37 +0100 (MET)
In-reply-to: "Bart Schaefer"'s message of Sat, 13 Feb 1999 16:30:57 -0800
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm

Bart Schaefer wrote:

> ...
>
> ... (with the usual caveats about contexts like
> parameter substitution that need some other key than "command name") ...

And before I forget to mention this: people using the new style
completion stuff may have noticed that completion after `$', `=', and
`~' still automagically works if complist is used independent of the
options given to it. This is due to the fact that this is still
handled very deeply in the completion code. I was thinking about
skipping over this code when the completion code is called from a
completion widget and instead testing for it and reporting this to the 
widget as different CONTEXTs. This sound like the correct behavior, right?

Bye
 Sven

--
Sven Wischnowsky                         wischnow@xxxxxxxxxxxxxxxxxxxxxxx

Messages sorted by: Reverse Date, Date, Thread, Author