From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh <zsh-workers@sunsite.dk>
Subject: Re: default tag-order (was Re: zsh 4.2.1-test-A)
Date: Sun, 8 Aug 2004 09:46:22 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0408080930430.16667@toltec.zanshin.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0408080837190.16667@toltec.zanshin.com>
On Sun, 8 Aug 2004, Bart Schaefer wrote:
> On Sun, 8 Aug 2004, Oliver Kiddle wrote:
>
> > The problem is with the default tag-order defined in _tags. The relevant
> > bit of code is as follows:
> > zstyle -a ":completion:${curcontext}:" tag-order order ||
> > order=('(|*-)argument-* (|*-)option[-+]* values' options)
> >
> > One safe option is to insert `(( ! ${@[(I)options]} )) ||'.
> > That checks if there is an options tag before applying the tag-order.
>
> I'm confused by this suggestion. If there's no options tag, the tag-order
> doesn't make any difference, because it's in the second group of tags.
> And in the case of cdrecord, there _is_ an options tag.
OK, I worked this out now. The problem is that there's no options tag *in
the argument-rest subcontext* but there are both values and files tags, so
the presence of values in this tag hides the files. Sorry to be dense.
The canonical examples of _values are _dd and _chmod, neither of which
allows ambiguity in whether an argument is a value or a filename (dd takes
only values, and chmod requires exactly one value before any filename).
So I suspect this simply never came up before.
next prev parent reply other threads:[~2004-08-08 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200408061350.i76DovBi028948@news01.csr.com>
2004-08-06 18:03 ` zsh 4.2.1-test-A Clint Adams
2004-08-07 13:40 ` Oliver Kiddle
2004-08-08 4:45 ` Clint Adams
2004-08-08 14:40 ` default tag-order (was Re: zsh 4.2.1-test-A) Oliver Kiddle
2004-08-08 16:03 ` Bart Schaefer
2004-08-08 16:46 ` Bart Schaefer [this message]
2004-08-08 17:25 ` Oliver Kiddle
2004-08-08 17:54 ` Oliver Kiddle
2004-08-10 18:16 ` 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=Pine.LNX.4.61.0408080930430.16667@toltec.zanshin.com \
--to=schaefer@brasslantern.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).