From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Misc. questions/remarks on new completion stuff
Date: Mon, 15 Feb 1999 10:31:55 +0100 (MET) [thread overview]
Message-ID: <199902150931.KAA23823@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Sat, 13 Feb 1999 16:50:25 -0800
Bart Schaefer wrote:
> I think "complist" could do with a better name. I've repeatedly been deluded
> into thinking that it's only used when generating completion listings, when
> really it adds possible matches that can be inserted on the command line.
Right, any suggestions, anyone? (Hm, `compgen' looks ugly.)
> Speaking of complist, what's the difference between
> compadd -m foo bar baz boing
> and
> complist -k '(foo bar baz boing)'
> ?? How much other overlap is there between these two commands?
Not much more. `compadd -m $...' is `complist -s '$...''. The overlap
was only caused by adding the `-m' option to `compadd' which I added
for the cases where one wants more control over the other strings and
flags stored with the matches and doesn't want to do the matching by
hand.
> In Functions/Completion/*, I think "#array" is a bad name for that tag. The
> "#function" tag means the function will actually generate matches, that is,
> call compadd or complist. But a "#array" file doesn't generate an array of
> matches -- it generates an array of arguments to complist. Why not use the
> tag "#complist" or "#complist-args" so it's more obvious what's going on?
I choose `#array' only to quickly finish the examples so that we can
play with them and didn't like it at the time, too. Although the
`#array' files have to set up an array (with the name of the file).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-02-15 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-15 9:31 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-14 0:50 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=199902150931.KAA23823@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).