From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: completion for perldoc
Date: Mon, 6 Sep 1999 13:37:14 +0200 (MET DST) [thread overview]
Message-ID: <199909061137.NAA01937@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Adam Spiers's message of Mon, 6 Sep 1999 11:07:20 +0100
Adam Spiers wrote:
> How would you define a suite of command exactly? I assumed it would
> be a function whose #compdef top line had many commands on it. My
> _perl* stuff has a #compdef line for the pm* commands from pmtools,
> and a #compdef for perldoc, but I couldn't figure out how to squash
> them all into one file.
Well, you can always compare `$words[1]' in an `if' or `case' and then
put the stuff from the #autoloaded functions in the same file and
execute it only if some parameter was set by the tests at the
beginning or something like that.
> I noticed Etc/Completion-style-guide soon after posting and realised
> the many problems with that _perl* :-(
Never mind. All this isn't fixed in stone yet and the `style-guide' is
quite new.
Bye
Sven
P.S.: And, after all, we are all still learning what is possible with
the function system.
P.P.S.: The function system started as an attempt to make the syntax
easier to understand. And now we have a completion function
that explains what it does by giving an equivalent `compctl' ;-)
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-09-06 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-06 11:37 Sven Wischnowsky [this message]
1999-09-06 18:18 ` Adam Spiers
1999-09-06 18:21 ` Adam Spiers
1999-09-07 8:57 ` Peter Stephenson
1999-09-07 9:18 ` Adam Spiers
-- strict thread matches above, loose matches on Subject: below --
1999-09-07 9:02 Sven Wischnowsky
1999-09-07 8:59 Sven Wischnowsky
1999-09-07 8:32 Sven Wischnowsky
1999-09-07 9:49 ` Adam Spiers
1999-09-06 9:28 Sven Wischnowsky
1999-09-06 10:07 ` Adam Spiers
1999-09-05 21:38 Adam Spiers
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=199909061137.NAA01937@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).