From: Adam Spiers <adam@spiers.net>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: 3.1.6-dev-22
Date: Tue, 11 Apr 2000 13:32:22 +0100 [thread overview]
Message-ID: <20000411133222.A24703@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <200004110828.KAA03835@beta.informatik.hu-berlin.de>; from wischnow@informatik.hu-berlin.de on Tue, Apr 11, 2000 at 10:28:05AM +0200
Sven Wischnowsky (wischnow@informatik.hu-berlin.de) wrote:
> Andrej Borsenkow wrote:
> > The decsription of compstate[insert] :
> >
> > ...
> > On exit it may be set to any of the values above (where
> > setting it to the empty string is the same as unsetting it),
> > or to a number, in which case the match whose number is given
> > will be inserted into the command line. It may also be set
> > to a string of the form `GROUP:MATCH' which specifies a match
> > from a group of matches to be inserted, counting from 1
> > upwards (e.g. `2:4' specifies the fourth match of the second
> > group). Negative numbers count backward from the last match
> > ... etc and the next paragraph
> >
> > Now, either I'm completely blind, or this is the _only_ place where
> > "number of group" is mentioned. This was there for a long time; I
> > presume, originally it was for sorted/unsorted matches - but
> >
> > - either it should be described, where these group numbers come from
> > - or, better yet, the name of group should be used.
>
> We have six name spaces for group names.
>
> The whole thing comes from a time when we were thinking about ways to
> get information about the matches already added. Then I was thinking
> about using it for the stuff that is now done with _next_tags. I
> didn't expect so much consistency and control in the shell code then.
>
> So, I would like to make the question: should we remove it? I would
> only comment it out in the C-code just in case we get a way to access
> matches added some day (not for a long time, I think).
>
> Actually, I was already tempted to remove it more than once and I
> don't think it would cause much harm (or any at all) -- noone has
> written another example completion system and the one we have doesn't
> use this feature.
Doesn't history-complete-word need this feature?
next prev parent reply other threads:[~2000-04-11 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 8:28 Sven Wischnowsky
2000-04-11 12:32 ` Adam Spiers [this message]
2000-04-11 15:48 ` Bart Schaefer
2000-04-11 20:19 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
2000-04-13 8:07 Sven Wischnowsky
2000-04-12 9:10 Sven Wischnowsky
2000-04-12 16:21 ` Bart Schaefer
2000-04-11 15:04 Sven Wischnowsky
2000-04-11 12:37 Sven Wischnowsky
2000-04-11 7:54 Sven Wischnowsky
2000-04-11 8:14 ` Andrej Borsenkow
2000-04-11 14:58 ` 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=20000411133222.A24703@thelonious.new.ox.ac.uk \
--to=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).