Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: _call (was: Re: PATCH: _diff (new), _prcs (upgrade))
- X-seq: zsh-workers 9536
- From: Alexandre Duret-Lutz <duret_g@xxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: _call (was: Re: PATCH: _diff (new), _prcs (upgrade))
- Date: 02 Feb 2000 17:51:02 +0100
- Cc: zsh-workers@xxxxxxxxxxxxxx
- In-reply-to: Sven Wischnowsky's message of "Wed, 2 Feb 2000 15:21:17 +0100 (MET)"
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <200002021421.PAA11232@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>> "Sven" == Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx> writes:
[...]
Sven> So, maybe we should just make
Sven> _call get the suggested command line and let users override them
Sven> completely or leave them alone. I would then make _call take a tag as
Sven> its first argument which is used to look up the style `command'
This looks easy to use.
[...]
Sven> The only problem is that -- in cases like the _diff -- the users would
Sven> have to know what the command has to do, but as long as we keep tags
Sven> and styles documented...
Could there be a way to make the completion
functions autodescribe themselve? (i.e.
print styles and tags used by the function,
as well as other info worth to know, in some
standard way). Perhaps it can be made by
using some special comments in the completions
functions and having a simple shell
function that take a command as argument,
that find the completion function
associated and format out these comments.
[...]
--
Alexandre Duret-Lutz
Messages sorted by:
Reverse Date,
Date,
Thread,
Author