comment #1:

> The second recipe...  Fantastic!  Disco!  :)

:)

> But... to avoid that entirely, maybe the Regex and Case toggles should be made oneshot toggles?  Just like the Backwards and Multibuffer toggles: only valid during the current menu invocation, and afterward falling back to whatever state was set in the nanorc file.
>

I've gotten used to the search feature being stateful, so that might be an unwelcome behavior change for users.  Other software, like Firefox and VS Code, remembers settings like "Whole Words" and "Match Case" between searches too.

I feel like this edge case doesn't really warrant a change in common search functionality.  The number of people who will be affected by a search change will be much greater than the number of users who will stumble upon this bug/oddity.

I tested the following steps with `nano --ignore`.

Steps to reproduce:
01 - Alt + :
02 - Alt + r
03 - Type {
04 - Press enter
05 - Type a
06 - Press enter
07 - Alt + :
08 - Alt + r
09 - Alt + r
10 - Press enter
--> A "Bad regex..." error message is displayed
11 - Alt + ;
--> A spurious "a" is inserted into the buffer


I discovered the above bug while narrowing down this (presumably related) hang:
01 - Alt + :
02 - Alt + r
03 - Type {
04 - Press enter
05 - Alt + ;
--> This is the only addition to the above steps
06 - Type a
07 - Press enter
08 - Alt + :
09 - Alt + r
10 - Alt + r
11 - Press enter
--> A "Bad regex..." error message is displayed
12 - Alt + ;
--> nano hangs


Version: 0e44752ba1474282cbc44a09afefee5c573e4878