Re: Using buffer for history-incremental-search-backward

[Felix Rosencrantz <f_rosencrantz@xxxxxxxxx>]

>While `sleep' is running, zle is inactive and the regular tty driver
>is in control of the interpretation of input characters.  Chances are
>you have `stty ^R redisplay' or the like (probably as a default, rather
>than explicitly in any of your init files), so the tty driver consumes
>the ^R before zle gets started again.

Opps...  Should have caught that myself.  That was the problem.  (Also
just noticed that the zsh's default stty completer doesn't know the
names used by the GNU stty.)

The function you provided works great.  (The example has a typo missing
the "al".)  I actually thought my h-i-s-b was still in the history
search, it sort of looked like it from the trace output....

>Both of these things could be considered bugs.

I think you're right that LASTWIDGET should probably be set correctly.
Though it would also be useful if there was a parameter that explicitly
says you are in the mini-buffer (or whatever the mode is).  Also,
it would useful if zle had the ability to specify bindings in the
mini-buffer and to somehow bless widgets as being safe to use in the
mini-buffer.

Zle still has a lot of little rough edges, like these problems with the
mini-buffer, and others like with widgets that try to handle multiline
command.  Or because zle can't update the prompt, it's not possible to
write a widget that does a cd, and have the prompt be correct.


So is there anyway to history-incremental-search-backward (and related
commands to show a list of matching commands.  Sort of like the w2k "F7"
key in a cmd.exe window.)

Thanks.
-FR.

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/