From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: 3.1.6-dev-22
Date: Tue, 11 Apr 2000 14:37:55 +0200 (MET DST) [thread overview]
Message-ID: <200004111237.OAA04834@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Adam Spiers's message of Tue, 11 Apr 2000 13:32:22 +0100
Adam Spiers wrote:
> ...
>
> > 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?
I was only talking about removing the group-number from
$compstate[insert]. h-c-w, like other functions in the completion
system, uses the match-number feature, without a group number. That
would be kept.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-04-11 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 12:37 Sven Wischnowsky [this message]
-- 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 8:28 Sven Wischnowsky
2000-04-11 12:32 ` Adam Spiers
2000-04-11 15:48 ` Bart Schaefer
2000-04-11 20:19 ` Peter Stephenson
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=200004111237.OAA04834@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).