You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider the sequence s\w+<ret> ... s<ret> ... s<ret>. The first s selects whole words, then the second s selects them again. The third s should have selected them once again (this is how it worked in v2023.08.05), instead it doesn't select anything as the empty string from the second s replaced the RE and shifted it to history. For this to work, now I have to recall the RE from history: s\w+<ret> ... s<ret> ... s<c-p><ret>. And if s<ret> were a part of a macro that macro would now fail after the first iteration.
More annoyingly, now fails the following, relatively common to me idiom: */<ret>n. * puts selections to the search register, then /<ret> selects the next occurrence after each selection, then n moves the main selection to the next occurrence after it. For this to work, now I have to repeat *: */<ret>*n.
It gets even more annoying if we're dealing with a more complicated RE that cannot be easily reproduced with *. E.g.
/\d+<ret>/<ret>N
/\d+<ret> selects a number, then /<ret> selects the next number after each selection, then N additionally selects another number after the main selection. For this to work, now I have to
/\d+<ret>/<ret>Z,/<c-p><ret><a-z>a
Outcome
After a search command with an empty RE was once used (s<ret>, /<ret>, etc.), subsequent similar searches don't find anything.
Expectations
The original RE is being kept in the search register, so that subsequent n, N, s<ret>, /<ret>, etc. continue to work.
Additional information
I guess either a2c4159 or c2fb073 may be relevant. Or both.
The text was updated successfully, but these errors were encountered:
Version of Kakoune
v2023.08.05-190-g9b166e80
Reproducer
Consider the sequence
s\w+<ret> ... s<ret> ... s<ret>
. The firsts
selects whole words, then the seconds
selects them again. The thirds
should have selected them once again (this is how it worked in v2023.08.05), instead it doesn't select anything as the empty string from the seconds
replaced the RE and shifted it to history. For this to work, now I have to recall the RE from history:s\w+<ret> ... s<ret> ... s<c-p><ret>
. And ifs<ret>
were a part of a macro that macro would now fail after the first iteration.More annoyingly, now fails the following, relatively common to me idiom:
*/<ret>n
.*
puts selections to the search register, then/<ret>
selects the next occurrence after each selection, thenn
moves the main selection to the next occurrence after it. For this to work, now I have to repeat*
:*/<ret>*n
.It gets even more annoying if we're dealing with a more complicated RE that cannot be easily reproduced with
*
. E.g./\d+<ret>
selects a number, then/<ret>
selects the next number after each selection, thenN
additionally selects another number after the main selection. For this to work, now I have toOutcome
After a search command with an empty RE was once used (
s<ret>
,/<ret>
, etc.), subsequent similar searches don't find anything.Expectations
The original RE is being kept in the search register, so that subsequent
n
,N
,s<ret>
,/<ret>
, etc. continue to work.Additional information
I guess either a2c4159 or c2fb073 may be relevant. Or both.
The text was updated successfully, but these errors were encountered: