1
1
mirror of https://github.com/wez/wezterm.git synced 2024-12-23 21:32:13 +03:00

docs for modifyOtherKeys

refs: https://github.com/wez/wezterm/issues/2527
This commit is contained in:
Wez Furlong 2022-09-20 09:11:52 -07:00
parent da13cf69fa
commit 182b6d148c
2 changed files with 17 additions and 1 deletions

View File

@ -24,7 +24,7 @@ As features stabilize some brief notes about them will accumulate here.
[strikethrough_position](config/lua/config/strikethrough_position.md) options
to fine tune appearance. [#2505](https://github.com/wez/wezterm/issues/2505)
[#2326](https://github.com/wez/wezterm/issues/2326)
* Preliminary support for `modifyOtherKeys` keyboard encoding
* Support for `modifyOtherKeys` keyboard encoding
[#2527](https://github.com/wez/wezterm/issues/2527)
* Superscript and subscript text attributes via SGR 73 and SGR 74
* [wezterm cli activate-pane-direction](cli/cli/activate-pane-direction.md)

View File

@ -15,6 +15,22 @@ That scheme has worked well for quite some time, but has some ambiguity due
to the way that the Control modifier "shifts" the ASCII representation of
keypresses like `Control-I` to be ASCII Tab, as an example.
## xterm `modifyOtherKeys`
*Since: nightly builds only*
When wezterm receives the sequence `CSI >4;Nm`, where `N` is `0`, `1` or `2`,
the keyboard encoding is changed according to
[modifyOtherKeys](https://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:modifyOtherKeys),
which causes certain modified keys to be encoded as [described in xterms
docs](https://invisible-island.net/xterm/modified-keys.html), making it
possible for applications to distinguish between the modified and unmodified
key presses.
Note that [enable_csi_u_key_encoding](lua/config/enable_csi_u_key_encoding.md)
and [allow_win32_input_mode](lua/config/allow_win32_input_mode.md) both take
precedence over this behavior.
## CSI-u/fixterms/libtickit
[Fix Keyboard Input on Terminals](http://www.leonerd.org.uk/hacks/fixterms/) is