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
I start swiper or swiper-isearch. I go to another finding in the mini-buffer (with C-n and C-p). I don't press Enter. Instead, I decide to cancel (C-g) the search. I am sent back to the point where I was when I started swiper. That's good, it's the intended behavior. There is explicit code to do that. See variable swiper-stay-on-quit which is described as "When non-nil don't go back to search start on abort.", and it's nil, so, the default behavior is indeed to go back on abort.
The bug
However, this isn't used by swiper-all and swiper-all.
So, if you navigate around in the mini-buffer with C-n and C-p, and (before pressing Enter) you press C-g, you'll be stuck where you last navigated, as if you had pressed Enter to actually go there.
The text was updated successfully, but these errors were encountered:
The expected behavior
I start
swiper
orswiper-isearch
. I go to another finding in the mini-buffer (withC-n
andC-p
). I don't press Enter. Instead, I decide to cancel (C-g
) the search. I am sent back to the point where I was when I startedswiper
. That's good, it's the intended behavior. There is explicit code to do that. See variableswiper-stay-on-quit
which is described as "When non-nil don't go back to search start on abort.", and it'snil
, so, the default behavior is indeed to go back on abort.The bug
However, this isn't used by
swiper-all
andswiper-all
.So, if you navigate around in the mini-buffer with
C-n
andC-p
, and (before pressing Enter) you pressC-g
, you'll be stuck where you last navigated, as if you had pressed Enter to actually go there.The text was updated successfully, but these errors were encountered: