If you live in the terminal, kitty is made for you! Cross-platform, fast, feature-rich, GPU based.
2e3f9dffa7
XKB has various options for using keys to switch the keyboard layout. When these are set, XKB will return keysyms which are unknown to GLFW, so kitty will fallback to using a keymap without the options set, which causes the keys to be interpreted as the original keysyms. However, when these options are set, kitty shouldn't interpret the keys. Therefore, check for some specific keysyms and return before translating to GLFW keysyms. There may be more keysyms which should be ignored, but as far as I can see from https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/blob/xkeyboard-config-2.29/symbols/group these are the ones which can be triggered by XKB options. Fixes #2519 |
||
|---|---|---|
| .github | ||
| docs | ||
| glad | ||
| glfw | ||
| kittens | ||
| kitty | ||
| kitty_tests | ||
| logo | ||
| terminfo | ||
| .gitattributes | ||
| .gitignore | ||
| .ignore | ||
| __main__.py | ||
| Brewfile | ||
| build-terminfo | ||
| CHANGELOG.rst | ||
| CONTRIBUTING.md | ||
| count-lines-of-code | ||
| gen-apc-parsers.py | ||
| gen-wcwidth.py | ||
| graphics-protocol.asciidoc | ||
| INSTALL.md | ||
| key_encoding.asciidoc | ||
| key_encoding.json | ||
| launcher.c | ||
| LICENSE | ||
| Makefile | ||
| mypy-editor-integration | ||
| protocol-extensions.asciidoc | ||
| publish.py | ||
| README.asciidoc | ||
| remote-control.asciidoc | ||
| session.vim | ||
| setup.cfg | ||
| setup.py | ||
| test.py | ||
| update-on-ox | ||
| update-on-ubuntu | ||
= kitty - the fast, featureful, GPU based, terminal emulator See https://sw.kovidgoyal.net/kitty/ image:https://github.com/kovidgoyal/kitty/workflows/CI/badge.svg["Build status", link="https://github.com/kovidgoyal/kitty/actions?query=workflow%3ACI"]