From: Adam Spiers <adam@spiers.net>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _files vs _path_files discussion (old thread)
Date: Sun, 12 Mar 2000 00:51:27 +0000 [thread overview]
Message-ID: <20000312005127.A28688@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <1000312001854.ZM26814@candle.brasslantern.com>; from schaefer@candle.brasslantern.com on Sun, Mar 12, 2000 at 12:18:53AM +0000
Bart Schaefer (schaefer@candle.brasslantern.com) wrote:
> On Mar 11, 10:22pm, Adam Spiers wrote:
> } Subject: Re: _files vs _path_files discussion (old thread)
> }
> } > > A second issue is whether, if you find target files in the current
> } > > directory, you might still want to complete directories.
> }
> } Does the new zstyle stuff now provide some kind of configurability to
> } solve this issue?
>
> Yes, it's the tag-order style.
Ah, so I was right after all.
> By putting all the tags in the same argument, they're all treated as
> equal for purposes of completions. You could also do
>
> zstyle ':completion::complete:tar::' \
> tag-order 'globbed-files directories' all-files
That's exactly what I'd tried, with once difference; as I mentioned, I
want this behaviour everywhere, not just for tar, so I'd tried:
zstyle ':completion::complete:*' \
tag-order 'globbed-files directories' all-files
However, neither your version nor mine seem to work. Maybe I'm just
missing a bugfix because I'm behind on patches.
Adam
next prev parent reply other threads:[~2000-03-12 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-17 7:28 PATCH: _rpm tweaks (_files vs _path_files discussion) Sven Wischnowsky
2000-03-11 22:22 ` _files vs _path_files discussion (old thread) Adam Spiers
2000-03-12 0:18 ` Bart Schaefer
2000-03-12 0:51 ` Adam Spiers [this message]
2000-03-12 6:21 ` Bart Schaefer
2000-03-12 6:34 ` Bart Schaefer
2000-03-12 13:02 ` Adam Spiers
2000-03-12 19:43 ` Bart Schaefer
2000-03-12 20:14 ` Adam Spiers
2000-03-12 22:51 ` Bart Schaefer
2000-03-13 13:07 Sven Wischnowsky
2000-03-13 17:54 ` Bart Schaefer
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=20000312005127.A28688@thelonious.new.ox.ac.uk \
--to=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.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).