You'll notice
Useful4 Signal1
Recalling an old prompt starting with ! or # no longer drops you into bash or memory mode.
What's wrong with this entry?
Anonymous. No account, no email.
What
Pressing up to bring back an earlier prompt that began with ! or # used to be treated as if you had just typed that character, switching the input into bash or memory mode. The recalled entry's own stored mode is now applied instead.
Details
- The prompt input's change handler takes a new option controlling whether a leading mode character is interpreted; the history-recall path is the only caller that turns it off.
- Recall now restores mode, pasted contents and cursor position together, and the history and history-search hooks take the draft object directly rather than a list of separate setters.
- Unconditional in the prompt input.
Evidence
interpretLeadingModeCharacter
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Editing a queued command keeps its mode and refuses on a dirty draft
Both mention input
-
v2.1.235
Enter no longer submits a text field in a select list, and arrows can leave the list
Both mention input
-
v2.1.235
Vim cursor position survives re-renders and editor round trips
Both mention input