j/.dZddlmZd dZd dZd dZdS) uAugmentations to prompt_toolkit's input-parsing tables. Imported once at CLI startup. Each helper installs a small mapping into prompt_toolkit's `ANSI_SEQUENCES` so byte sequences emitted by modern keyboard protocols (Kitty / xterm `modifyOtherKeys`) decode to existing key tuples Hermes already binds. Kept in a standalone module — separate from `cli.py` — so the registrations can be unit-tested without importing the whole CLI runtime. ) annotationsreturnintc ddlm}ddlm}n#t$rYdSwxYw|j|jf}d}dD]%}|||kr |||<|dz }&|S)uMap Shift+Enter byte sequences to the (Escape, ControlM) key tuple that Alt+Enter produces, so the existing Alt+Enter newline handler fires for terminals that emit a distinct Shift+Enter. Sequences mapped: - "\x1b[13;2u" — Kitty keyboard protocol / CSI-u, modifier=2 (Shift) - "\x1b[27;2;13~" — xterm modifyOtherKeys=2, modifier=2 (Shift) - "\x1b[27;2;13u" — alternate ordering some emitters use The CSI-u sequence is not in stock prompt_toolkit. The modifyOtherKeys variant `\x1b[27;2;13~` IS in stock prompt_toolkit but mapped to plain `Keys.ControlM` — i.e. Shift+Enter behaves identically to Enter, which is the very bug this helper exists to fix. We therefore overwrite those two specific keys (and `\x1b[27;2;13u`) unconditionally; other `\x1b[27;...;13~` sequences (Ctrl+Enter, Alt+Enter via modifyOtherKeys variants 5/6/etc.) are left untouched. Default macOS Terminal and stock Windows Terminal still send the same byte for Enter and Shift+Enter, so there is no fix for those terminals at the application layer — the sequences above never reach Hermes. Returns the number of sequences whose mapping was changed. rANSI_SEQUENCESKeys)zz [27;2;13~z *prompt_toolkit.input.ansi_escape_sequencesrprompt_toolkit.keysr ExceptionEscapeControlMgetrr alt_enterchangedseqs ?/home/ubuntu/.hermes/hermes-agent/hermes_cli/pt_input_extras.pyinstall_shift_enter_aliasrs0MMMMMM,,,,,,, qqdm,IG?   c " "i / /"+N3  qLG N  c ddlm}ddlm}n#t$rYdSwxYw|j|jf}d}dD]%}|||kr |||<|dz }&|S)uMap Ctrl+Enter byte sequences to the (Escape, ControlM) key tuple that Alt+Enter produces, so the existing Alt+Enter newline handler fires for terminals that emit a distinct Ctrl+Enter. Sequences mapped: - "\x1b[13;5u" — Kitty keyboard protocol / CSI-u, modifier=5 (Ctrl) - "\x1b[27;5;13~" — xterm modifyOtherKeys=2, modifier=5 (Ctrl) - "\x1b[27;5;13u" — alternate ordering some emitters use Stock prompt_toolkit doesn't map any of these. Without this alias, Kitty/mintty/xterm-with-modifyOtherKeys users over SSH never get a Ctrl+Enter newline — the keystroke arrives as a raw CSI sequence that falls through to the default character-insert handler. See #22379. Returns the number of sequences whose mapping was changed. rrr )zz [27;5;13~z r r rs rinstall_ctrl_enter_aliasr6s"MMMMMM,,,,,,, qqdm,IG?   c " "i / /"+N3  qLG Nrcx ddlm}ddlm}n#t$rYdSwxYwd}dD]}||vr|j||<|dz }|S)uMap terminal-emitted noise sequences to ``Keys.Ignore`` so they are consumed by the VT100 parser before they reach key bindings or the input buffer. Currently covers focus reports: - ``\x1b[I`` — terminal regained focus (focus in) - ``\x1b[O`` — terminal lost focus (focus out) Ghostty, iTerm2, and some xterm builds can emit these sequences when the user switches tabs / windows or when a multiplexer toggles focus tracking upstream. prompt_toolkit does not map these by default, so its parser falls back to literal key presses (ESC, ``[``, ``I``/``O``) and inserts ``[I``/``[O`` into the prompt buffer after the ESC byte is handled. Registering them as ``Keys.Ignore`` is parser-level — strictly cleaner than post-hoc regex stripping in the input sanitizer because the bytes never reach the buffer. ``setdefault`` is used so any user or downstream registration wins. Returns the number of sequences whose mapping was changed. rrr )zzr )r rrr rIgnore)rr rrs r"install_ignored_terminal_sequencesrVs.MMMMMM,,,,,,, qqG# n $ $"&+N3  qLG NrN)rr)__doc__ __future__rrrrrr#sk  #"""""$$$$N@""""""r"