{"version":"2.1.247","anchor":"escape-key-sequences-split-across-two-terminal-reads-are-no-","canonical_anchor":"escape-key-sequences-split-across-two-terminal-reads-are-no-","heading":"Escape key sequences split across two terminal reads are no longer garbled","tier":"notice","area":"Terminal Input","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/escape-key-sequences-split-across-two-terminal-reads-are-no-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Escape key sequences split across two terminal reads are no longer garbled\n\nKeypresses split across terminal reads no longer leak stray escape characters into your input.\n\n**What**\n\nWhen a key sequence arrives split so that only a bare Escape (or Escape-bracket) is left in the buffer, the decoder now remembers that fragment and joins it to the next chunk, emitting one key or mouse event instead of a stray Escape followed by stray literal characters.\n\n**Details**\n\n- The remembered fragment is cleared as soon as a complete sequence arrives.\n- It is not applied inside a paste, so pasted text is unaffected.\n\n**Evidence**\n\n`flushedEscapePrefix`\n\n- Area: Terminal Input\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}