mirror of
https://github.com/kovidgoyal/kitty
synced 2026-07-10 14:14:48 +02:00
Dont turn on disambiguate keys when receiving th XTMODKEYS escape code
See #4075
This commit is contained in:
@@ -69,6 +69,11 @@ To update |kitty|, :doc:`follow the instructions <binary>`.
|
||||
applying to all windows, not just the initially created ones. Note that
|
||||
``--watcher`` now also applies to all windows, not just initially created ones.
|
||||
|
||||
- **Backward incompatibility**: No longer turn on the kitty extended keyboard
|
||||
protocol's disambiguate mode when the client sends the XTMODKEYS escape code.
|
||||
Applications must use the dedicated escape code to turn on the protocol.
|
||||
(:iss:`4075`)
|
||||
|
||||
|
||||
0.23.1 [2021-08-17]
|
||||
----------------------
|
||||
|
||||
@@ -277,13 +277,6 @@ oldest entry from the stack must be evicted.
|
||||
the editor would have to somehow know what the keyboard mode of the main
|
||||
screen is and restore to that mode on exit.
|
||||
|
||||
.. note:: In the interests of interoperation, the XTerm specific sequences
|
||||
``CSI > 4; x m`` and ``CSI > 4; 0 m`` are treated as ``CSI > 1 u`` and ``CSI
|
||||
< 1 u``. Here ``x`` can be either ``1`` or ``2``. These codes cause XTerm
|
||||
to use the CSI u encoding for more keys and are therefore treated as similar
|
||||
to the disambiguate progressive enhancement.
|
||||
|
||||
|
||||
.. _disambiguate:
|
||||
|
||||
Disambiguate escape codes
|
||||
|
||||
Reference in New Issue
Block a user