From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Redirection completion
Date: Fri, 08 Mar 2002 14:06:45 +0000 [thread overview]
Message-ID: <22196.1015596405@csr.com> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Fri, 08 Mar 2002 13:54:17 +0100." <15496.46201.219885.149096@wischnow.berkom.de>
Aargh, forgot to send this to the list again.
Sven Wischnowsky wrote:
> (should I
> also include the change to make compdef() use _comp_assocs? saving you
> some time?)
You might as well, it's certainly less than urgent and you might notice
something I wouldn't.
Oliver wrote:
>> Along the lines of
>> :completion::complete:dvips:option-o-1:
>> I would suggest
>> :completion::complete:echo:redir-2>:'
>> for `echo 2>'.
>
> The context isn't too useful for values either. I'm not sure about
> putting the information in the fifth (argument) part of the context.
> For values the fourth (command) part is just set to -value-. What I
> would suggest is that we use the fourth part of the context.
>...
>
>:completion::complete:-redirect-echo-2>:
>:completion::complete:-value-GZIP:
I don't understand the reasoning: why does this need to be different
from the way options or arguments work? For redirection it would seem
to be a similar sort of case, where you might want to match on the
command name in the normal way. Values certainly demand different
handling. But then surely the logical thing is to keep the type
separate from the argument and have
:completion::complete:-value-:GZIP:
as the context?
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 392070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
next prev parent reply other threads:[~2002-03-08 14:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 12:33 Peter Stephenson
2002-03-08 12:54 ` Sven Wischnowsky
2002-03-08 14:06 ` Peter Stephenson [this message]
2002-03-08 14:10 ` Sven Wischnowsky
2002-03-11 8:42 ` Sven Wischnowsky
2002-03-11 9:58 ` Sven Wischnowsky
2002-03-11 10:54 ` Peter Stephenson
2002-03-11 11:16 ` Sven Wischnowsky
2002-03-11 11:29 ` Peter Stephenson
2002-03-11 12:08 ` Sven Wischnowsky
2002-03-11 14:01 ` Peter Stephenson
2002-03-11 16:56 ` Bart Schaefer
2002-03-12 9:03 ` Sven Wischnowsky
2002-03-12 13:16 ` Oliver Kiddle
2002-03-13 9:25 ` Sven Wischnowsky
2002-03-13 16:55 ` Peter Stephenson
2002-03-14 12:03 ` Sven Wischnowsky
2002-03-13 17:58 ` Oliver Kiddle
2002-03-13 18:19 ` Bart Schaefer
2002-03-14 13:51 ` Oliver Kiddle
2002-03-14 14:41 ` Peter Stephenson
2002-03-14 14:43 ` Sven Wischnowsky
2002-03-08 13:20 ` Oliver Kiddle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22196.1015596405@csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).