From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: Sven Wischnowsky <wischnow@berkom.de>, zsh-workers@sunsite.dk
Subject: Re: Menu selection
Date: Wed, 29 May 2002 09:44:03 -0700 (PDT) [thread overview]
Message-ID: <20020529164403.52651.qmail@web10406.mail.yahoo.com> (raw)
In-Reply-To: <15603.16487.588260.866988@wischnow.berkom.de>
--- Sven Wischnowsky wrote:
> I had been thinking about that, too, and, if it's going to be
> incremental searching -- which it should -- it's not entirely trivial
> to implement. ....
>
> It makes completion be re-tried after every selfinsert-key. This is a
> bit like incremental searchin, only that the whole completion list
> changes to include only the set of possible matches.
> character into the line). And probably a way to set the default
> behaviour (i.e. when menu selection is first entered).
I frequently use the "history-incremental-search-backward" zle widget.
And I find that I would really like the power of matching control. (I
use completion with matching control even more frequently, so I've
started to type with pivot points in mind.) So if I have history like:
% mount_work read-only
% cd /work
% more README
% cd /tmp
% unmount_work
If I do a "history-incremental-search-backward" with "m_w", it would
find the "mount_work" command line if my matching spec makes the "_" a
pivot character. (Likewise, "u_w" would find unmount_work, and "r-o"
would find the mount_work command.)
It seems like what you are suggesting will make something like
this possible. I hope this incremental searching could be used in an
alternative widget to the "history-incremental-search-backward" widget,
but with matching control.
I think one of the other problems with trying to use completion for a
"history-incremental-search-backward" alternative, is the need of completion
to quote&blackslash multi-word completions.
-FR.
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
next prev parent reply other threads:[~2002-05-29 16:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 8:31 Sven Wischnowsky
2002-05-28 10:44 ` Oliver Kiddle
2002-05-28 11:24 ` Sven Wischnowsky
2002-05-28 12:08 ` Peter Stephenson
2002-05-29 11:23 ` Sven Wischnowsky
2002-05-29 11:30 ` Peter Stephenson
2002-05-29 16:44 ` Felix Rosencrantz [this message]
2002-06-18 7:57 Sven Wischnowsky
2002-06-18 9:51 ` Oliver Kiddle
2002-06-19 7:49 ` Sven Wischnowsky
2002-06-20 15:52 ` Oliver Kiddle
2002-06-20 15:58 ` Bart Schaefer
2002-06-20 16:22 ` Oliver Kiddle
2002-06-21 9:27 ` Sven Wischnowsky
2002-06-26 10:18 ` Sven Wischnowsky
[not found] <15642.49846.468542.689062@wischnow.berkom.de>
[not found] ` <20020627182621.70670.qmail@web10405.mail.yahoo.com>
2002-07-03 7:58 ` Sven Wischnowsky
2002-07-04 9:27 ` Sven Wischnowsky
2002-07-04 17:56 ` Felix Rosencrantz
2002-07-05 8:09 ` Sven Wischnowsky
2002-07-24 23:01 ` Felix Rosencrantz
2002-07-30 7:47 ` Sven Wischnowsky
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=20020529164403.52651.qmail@web10406.mail.yahoo.com \
--to=f_rosencrantz@yahoo.com \
--cc=wischnow@berkom.de \
--cc=zsh-workers@sunsite.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).