From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: Completion and command versions
Date: Fri, 14 Mar 2003 10:30:14 +0000 [thread overview]
Message-ID: <28975.1047637814@csr.com> (raw)
In-Reply-To: "Doug Kearns"'s message of "Fri, 14 Mar 2003 11:14:50 +1100." <20030314001450.GE954@localhost.localdomain>
Doug Kearns wrote:
> Is there a policy regarding the command version that completion
> functions should support? What about commands where there are
> significant changes between versions?
The standard way is using the _pick_variant function.
If it's too dangerous to run the command to find out what it does, you
probably need a style. `variant' is already use by _pick_variant,
unfortunately --- it's not a very good name, since it doesn't give the
variant, it gives the programme to run to pick the variant. Of course
it could be set to a function that simply returns the type, but that
method doesn't have a sensible default.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
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:[~2003-03-14 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 0:14 Doug Kearns
2003-03-14 10:30 ` Peter Stephenson [this message]
2003-03-14 11:58 ` Oliver Kiddle
2003-03-19 13:45 ` 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=28975.1047637814@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).