§
    ãFj/  ã                  ó.   — d Z ddlmZ d	d„Zd	d„Zd	d„ZdS )
u½  Augmentations 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.
é    )ÚannotationsÚreturnÚintc                 ó´   — 	 ddl m}  ddlm} n# t          $ r Y dS w xY w|j        |j        f}d}dD ]%}|                      |¦  «        |k    r
|| |<   |dz  }Œ&|S )uÃ  Map 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.
    r   ©ÚANSI_SEQUENCES©ÚKeys)z[13;2uz
[27;2;13~z
[27;2;13ué   ©Ú*prompt_toolkit.input.ansi_escape_sequencesr   Úprompt_toolkit.keysr
   Ú	ExceptionÚEscapeÚControlMÚget©r   r
   Ú	alt_enterÚchangedÚseqs        ú9/usr/local/lib/hermes-agent/hermes_cli/pt_input_extras.pyÚinstall_shift_enter_aliasr      s¦   € ð0ØMÐMÐMÐMÐMÐMØ,Ð,Ð,Ð,Ð,Ð,Ð,øÝð ð ð Øˆqˆqðøøøð ”˜dœmÐ,€IØ€GØ?ð ð ˆØ×Ò˜cÑ"Ô" iÒ/Ð/Ø"+ˆN˜3ÑØq‰LˆGøØ€Nó   ‚ 
œc                 ó´   — 	 ddl m}  ddlm} n# t          $ r Y dS w xY w|j        |j        f}d}dD ]%}|                      |¦  «        |k    r
|| |<   |dz  }Œ&|S )u  Map 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.
    r   r   r	   )z[13;5uz
[27;5;13~z
[27;5;13ur   r   r   s        r   Úinstall_ctrl_enter_aliasr   6   s¦   € ð"ØMÐMÐMÐMÐMÐMØ,Ð,Ð,Ð,Ð,Ð,Ð,øÝð ð ð Øˆqˆqðøøøð ”˜dœmÐ,€IØ€GØ?ð ð ˆØ×Ò˜cÑ"Ô" iÒ/Ð/Ø"+ˆN˜3ÑØq‰LˆGøØ€Nr   c                 óx   — 	 ddl m}  ddlm} n# t          $ r Y dS w xY wd}dD ]}|| vr|j        | |<   |dz  }Œ|S )uò  Map 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.
    r   r   r	   )z[Iz[Or   )r   r   r   r
   r   ÚIgnore)r   r
   r   r   s       r   Ú"install_ignored_terminal_sequencesr   V   sŒ   € ð.ØMÐMÐMÐMÐMÐMØ,Ð,Ð,Ð,Ð,Ð,Ð,øÝð ð ð Øˆqˆqðøøøð €GØ#ð ð ˆØnÐ$Ð$Ø"&¤+ˆN˜3ÑØq‰LˆGøØ€Nr   N)r   r   )Ú__doc__Ú
__future__r   r   r   r   © ó    r   ú<module>r#      sk   ðð	ð 	ð #Ð "Ð "Ð "Ð "Ð "ð$ð $ð $ð $ðNð ð ð ð@"ð "ð "ð "ð "ð "r"   