{"version":"2.1.247","anchor":"recalling-a-prompt-starting-with-or-no-longer-flips-input-mo","canonical_anchor":"recalling-a-prompt-starting-with-or-no-longer-flips-input-mo","heading":"Recalling a prompt starting with ! or # no longer flips input modes","tier":"notice","area":"Input Box","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/recalling-a-prompt-starting-with-or-no-longer-flips-input-mo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Recalling a prompt starting with `!` or `#` no longer flips input modes\n\nRecalling an old prompt starting with ! or # no longer drops you into bash or memory mode.\n\n**What**\n\nPressing 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.\n\n**Details**\n\n- 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.\n- 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.\n- Unconditional in the prompt input.\n\n**Evidence**\n\n`interpretLeadingModeCharacter`\n\n- Area: Input Box\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 1\/5"}