|
From: | Farblos |
Subject: | bug#62032: 28.2; `switch-frame' event exits incremental search |
Date: | Tue, 7 Mar 2023 22:11:23 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 |
This looks related to bug#41338 that is still unfixed. But maybe 'ignore is really the right way to fix, this needs testing.Agreed, but bug#41338 seems to imply that the comment from isearch.el quoted above is wrong or misleading and that a frame switch should actually exit an incremental search. In which case this bug would be a wontfix.I'm fine with that point of view as long as I'm allowed to let frame switches keep isearch alive in some way or other. I understand that the buffer switch (resulting from the frame switch) during an isearch is evil, but I frequently just alt-tab to a different frame, peek something there, alt-tab back, and continue the isearch.
Um, I just tried to not "only peek something" in the second frame, but rather type some text, which is of course grabbed by the isearch running in the first frame, which is of course highly confusing.
Having tested that, I'd rather vote for wontfix for this bug, hoping that I can continue to bind `ignore´ to `switch-frame´ in my very personal configuration for more versions to come to keep the behavior as I am used to it.
[Prev in Thread] | Current Thread | [Next in Thread] |