From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: RE: PATCH: hidden matches in menu-select
Date: Wed, 8 Dec 1999 10:49:00 +0100 (MET) [thread overview]
Message-ID: <199912080949.KAA17251@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Wed, 8 Dec 1999 12:39:06 +0300
Andrej Borsenkow wrote:
> > And: should we try to change what is
> > displayed for those multiple-matches-with-the-same-display-string?
> >
>
> I am mot sure if you mean the same thing ... Of course, it would be nice to see
> "context" for those matches (or, more generally, how they differ). The
> alternatives off head may be
>
> - kind of status line. This may also be used to display per-item help string or
> like. This probably will require significant changes in the code.
This isn't exactly useful, because if you move the cursor over one of
those multi-matches, you'll of course see the difference -- because
then the match is inserted in the line.
The question is if we need to display the differences in the list
itself. One reason I forgot to mention why I didn't spend more time
trying to implement that is: this doesn't happen very often. You'll
probably find some examples for when it does happen with _path_files.
Indeed, I'm almost expecting some more `bug' reports for it from you
after this patch ;-)
> - grouping of matches with the same context. Of course, combining it with any
> user-defined grouping may be ehh ... tricky.
That's why I didn't use Peter's suggestion of stuffing all those
matches in an extra group (we would have to use multiple extra
sub-groups, I think).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-12-08 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-08 9:49 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-12-08 13:49 Sven Wischnowsky
1999-12-08 9:08 Sven Wischnowsky
1999-12-08 9:39 ` Andrej Borsenkow
1999-12-08 10:13 ` 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=199912080949.KAA17251@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).