From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Adam Spiers <adam@spiers.net>, zsh-workers@sunsite.auc.dk
Subject: Re: _files vs _path_files discussion (old thread)
Date: Sun, 12 Mar 2000 00:18:53 +0000 [thread overview]
Message-ID: <1000312001854.ZM26814@candle.brasslantern.com> (raw)
In-Reply-To: <20000311222225.A27795@thelonious.new.ox.ac.uk>
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.
} Suppose I have, in the cwd, a file `foo.tar.gz' and a directory `foo'.
} I type:
}
} $ tar zxf foo<TAB>
}
} Currently, this immediately completes to `foo.tar.gz'. But what if I
} actually wanted to extract a .tar.gz from somewhere within the
} directory foo?
zstyle ':completion::complete:tar::' \
tag-order 'globbed-files directories all-files'
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 is, put all-files in a separate argument) to get shown all possible
files only if there are no globbed-files or directories. The default is
as if you had
zstyle ':completion::complete:tar::' \
tag-order globbed-files directories all-files
(that is, all in separate arguments), which in turn depends on some of
the command-line options passed to _files by _tar (so it's not the same
for all completions that use _files).
} Incidentally, the more I understand of the new completion system, the
} more I like it. [...] Congratulations to everyone involved,
} especially (needless to say) Sven!
Right, three cheers for Sven! And thanks.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-03-12 0:19 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 [this message]
2000-03-12 0:51 ` Adam Spiers
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=1000312001854.ZM26814@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=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).