* Bug in history-beginning-search-* in 4.2.0
@ 2004-03-24 16:39 Bart Schaefer
0 siblings, 0 replies; only message in thread
From: Bart Schaefer @ 2004-03-24 16:39 UTC (permalink / raw)
To: zsh-workers
Starting with:
schaefer<504> eval echo this is a test line
this is a test line
schaefer<505> echo this is a second test line
this is a second test line
I now invoke predict-on and type e v backspace:
schaefer<506> echo this is a second test line
schaefer<506> eval echo this is a test line
schaefer<506> evcho this is a second test line
Note that history-beginning-search-forward worked correctly, but the
new text it inserted failed to overwrite the "v". For some reason the
((--CURSOR)) in delete-backward-and-predict didn't stick.
This appears to be a bug in history-beginning-search-*. Given this
simple widget:
back-and-search-forward () {
((--CURSOR))
zle .history-beginning-search-forward
}
I can reproduce the above bug with history-beginning-search-backward
followed by back-and-search-forward.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-03-24 16:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-24 16:39 Bug in history-beginning-search-* in 4.2.0 Bart Schaefer
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).