mirror of
https://github.com/SpartanJ/eepp.git
synced 2026-10-18 03:23:28 +03:00
Martín Lucas Golini
ee0d9378ad
Add guides for native UI authoring, layouts, application CSS, and HTML compatibility. Update the CSS reference, rename article files consistently, and point README links to the local guides. Add Copy Link for HTML and Markdown anchors when no text is selected. Resolve relative links against the document URI before copying, and cover Markdown and WebView behavior with tests. Fix layout width policy serialization to use the widget's width.
18 lines
1.1 KiB
Markdown
18 lines
1.1 KiB
Markdown
# eterm Kitty keyboard protocol
|
|
|
|
eterm implements Kitty keyboard protocol progressive enhancement. Applications negotiate it at
|
|
runtime with `CSI ? u`, `CSI > flags u`, `CSI < count u`, and `CSI = flags ; mode u`; changing
|
|
`TERM` to `xterm-kitty` is neither necessary nor recommended.
|
|
|
|
The implementation accepts all standardized flags. Main and alternate screens have independent
|
|
bounded mode stacks. Alternate-key reporting derives the standard PC-layout key from EEPP's
|
|
layout-independent scancode and the shifted key from committed text. Associated committed text is
|
|
reported when available from text input.
|
|
|
|
SDL2 and SDL3 repeat markers are preserved, so press, repeat, and release events are distinct when
|
|
event reporting is enabled. IME pre-edit input remains local; only committed text is forwarded.
|
|
|
|
For a raw diagnostic, an application can push report-all mode with `ESC [ > 8 u`. In that mode,
|
|
Ctrl+Enter is sent as `ESC [ 13 ; 5 u`. It must pop the mode with `ESC [ < u` before exiting.
|
|
Intermediaries such as tmux or screen must independently support and forward the protocol.
|