Commit 57413abb authored by Kovid Goyal's avatar Kovid Goyal

Clarify handling of multi-key compose sequences

parent d5f9d0d5
...@@ -70,7 +70,11 @@ The new mode works as follows: ...@@ -70,7 +70,11 @@ The new mode works as follows:
the US layout on a mac would generate the UTF-8 bytes for the ∫ symbol. the US layout on a mac would generate the UTF-8 bytes for the ∫ symbol.
This way terminal applications do not need to care about keyboard layouts This way terminal applications do not need to care about keyboard layouts
or extended input modes, text entry even for arbitrary keyboard layouts and or extended input modes, text entry even for arbitrary keyboard layouts and
languages, just works, out of the box. languages, just works, out of the box. Note that this also applies to
so called "dead-keys" or compose sequences. So if there is a multi-key
sequence that yields some text, only that text must be sent, as UTF-8.
If the multi-key sequence is canceled, then the terminal emulator should
follow platform conventions about whether to send the partial keys or not.
* For non printable keys and key combinations including one or more modifiers, * For non printable keys and key combinations including one or more modifiers,
an escape sequence encoding the key event is sent. For details on the an escape sequence encoding the key event is sent. For details on the
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment