mirror of
https://github.com/kovidgoyal/kitty.git
synced 2025-12-13 20:36:22 +01:00
16008b950a343ece4b45089a25de076af1379e94
On compositors that support compositor key repeat events, use those, for complete robustness. Sadly no actual compositor implements these yet. Otherwise use a timer fd/pipe to queue the repeat events and only dispatch them after events from the compositor are handled. This means release events from the compositor will prevent spurious repeat events. One can, in the worst case lose some repeat events if there is a very large interval between the start of the timer and the next poll, but that is unavoidable and is why repeat events should come from the compositor in the first place. Fixes #9224
Wayland: Fix spurious key repeat events when some user defined callback takes a long time to execute
Wayland: Fix spurious key repeat events when some user defined callback takes a long time to execute
= kitty - the fast, feature-rich, cross-platform, GPU based terminal If you live in the terminal, *kitty* is made for **you**! See https://sw.kovidgoyal.net/kitty/[the kitty website]. image:https://github.com/kovidgoyal/kitty/workflows/CI/badge.svg["Build status", link="https://github.com/kovidgoyal/kitty/actions?query=workflow%3ACI"] https://sw.kovidgoyal.net/kitty/faq/[Frequently Asked Questions] To ask other questions about kitty usage, use either the https://github.com/kovidgoyal/kitty/discussions/[discussions on GitHub] or the https://www.reddit.com/r/KittyTerminal[Reddit community] Packaging status in various repositories: image:https://repology.org/badge/vertical-allrepos/kitty-terminal.svg?columns=3&header=kitty["Packaging status", link="https://repology.org/project/kitty-terminal/versions"]
Languages
Python
38.9%
C
28.1%
Go
25.8%
Objective-C
5.4%
Shell
1.1%
Other
0.6%