From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _a2ps completion
Date: Tue, 18 Jan 2000 11:17:27 +0100 (MET) [thread overview]
Message-ID: <200001181017.LAA30106@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Clint Adams's message of Mon, 17 Jan 2000 10:28:38 -0500
[ Our name-server was down this morning, and the answer I sent to this
seems to have disappeared. Sorry if it re-appears and you get this
twice. ]
Clint Adams wrote:
> I have been informed that a2ps can be just as useful on PostScript
> files as any other file, and that *.(#i)(ps|eps) should not be
> excluded from completion. Perhaps a context-based switch would
> be more appropriate.
>
> ...
>
> -_arguments '*:text file:_files -g \*\~\*.\(\#i\)\(ps\|eps\)' -- \
> +_arguments '*:input file:_files' -- \
I'm really, really against this change.
After all, we use _files to be able to 1) restrict the types of files
matched to some sensible subset and to 2) still be able to complete
other files as a default. And since in many (I think: most) cases one
won't want to a2ps postscript files, we should definitely keep the old
form.
*And* for exactly this kind of stuff we added the tags mechanism,
dammit. So, if RTM isn't clear, someone should document (at the top of
_a2ps?) that one can easily say that one wants to complete all files
for a2ps (or any other command) by just saying:
zstyle ':completion:*::a2ps:*' tag-order all-files
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-01-18 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-18 10:17 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-19 16:16 Sven Wischnowsky
2000-01-18 13:17 Sven Wischnowsky
2000-01-18 20:00 ` Peter Stephenson
2000-01-18 12:06 Sven Wischnowsky
2000-01-18 11:30 Sven Wischnowsky
2000-01-18 11:46 ` Zefram
2000-01-18 11:50 ` Akim Demaille
2000-01-18 11:00 Akim Demaille
2000-01-18 11:32 ` Akim Demaille
2000-01-18 8:08 Sven Wischnowsky
2000-01-17 15:28 Clint Adams
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=200001181017.LAA30106@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).