From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Cc: pws@ifh.de
Subject: Re: completion functions (was: 6-pws-2)
Date: Thu, 2 Sep 1999 13:11:21 +0200 (MET DST) [thread overview]
Message-ID: <199909021111.NAA03078@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Wed, 01 Sep 1999 15:56:11 +0200
Peter Stephenson wrote:
> Sven Wischnowsky wrote:
> > With a little help from `awk' this was relatively easy to build, so I
> > thought I just try to make us make a decision.
> >
> > This is `User/_pbm' again, but containing mostly the stuff from the
> > `Pbmplus/*' files.
>
> I like it this way --- particularly since it replaces a 100 functions, and
> you can compare the different behaviour for each function just by looking
> through the one file. Does anyone have anything to say for the other way,
> before I delete the Pbmplus subdirectory? Also, would it help to add a
> comment pointing out you can override individual completions by defining an
> appropriate function?
Maybe. Just to rub it in.
Bye
Sven
diff -u Completion.old/User/_pbm Completion/User/_pbm
--- Completion.old/User/_pbm Thu Sep 2 11:37:39 1999
+++ Completion/User/_pbm Thu Sep 2 13:10:15 1999
@@ -1,5 +1,11 @@
#compdef -P (p[bgpn]m*|*top[bgpn]m)
+# Completion for all (or most, you'll never know) pbmplus commands.
+# For some of them there are special cases in the biggish `case' below.
+# Note that since this function is a post-pattern function, these
+# defaults can be overridden by simple defining completion functions
+# for those commands whose arguments you want to complete differently.
+
local pat expl ret=1
if [[ "$words[1]" = pnm* ]]; then
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-09-02 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-02 11:11 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-01 13:19 Sven Wischnowsky
1999-09-01 13:56 ` Peter Stephenson
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=199909021111.NAA03078@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=pws@ifh.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).