Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: compinit/compdef useful outside of completion?
- X-seq: zsh-workers 6918
- From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: compinit/compdef useful outside of completion?
- Date: Tue, 29 Jun 1999 14:03:16 +0200 (MET DST)
- In-reply-to: "Andrej Borsenkow"'s message of Tue, 29 Jun 1999 15:47:25 +0400
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
Andrej Borsenkow wrote:
> Don't you think, that these can be used not only with completion widgets? I
> actually like the idea, when I just need to drop a file in defined place and it
> will automatically be used next time I start shell. No more .zshrc editing etc.
>
> What I mean, does it make sense to extend compinit/compdef to handle "normal"
> user defined widgets as well ('course, the names will probably be too misleading
> ...). E.g. 'compdef -w widget function' to define normal widget. You could even
> automatically bind it to key sequence with additional parameter ... say "-k
> ^Xn"?
> And start function with '#compdef -w <widget>'
I've been thinking about this, too. Some kind of autoauto-functions
with arguments describing the tags to expect and what to do with
them. Or some external configuration and then cal autoauto or
whatever. (Heck, haven't I mentioned that yet? I thought I had, but
maybe I've been only thinking too much about it.)
This is even more interesting if we once get into heavy widget-hacking.
What I'm currently thinking about is how we could generalise the
dumping code and integrate it with a generic autoauto function.
Bye
Sven
--
Sven Wischnowsky wischnow@xxxxxxxxxxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author