aboutsummaryrefslogtreecommitdiff
path: root/unicode-mode.c (unfollow)
Commit message (Collapse)AuthorLines
2026-07-21ime: refresh search matches after IME commit0WD0-2/+3
The IME commit handler appended text to the search buffer and refreshed the search box, but never called search_find_next(). CJK input into scrollback search therefore showed no match until another key press re-triggered the regular search input path. Call search_find_next() in the commit branch, and apply the same fix to unicode-mode.c. To allow this, search_find_next() is no longer static.
2026-05-12search/url/unicode-mode: set last-shortcut-symDaniel Eklöf-0/+2
When processing shortcuts, set seat->kbd.last_shortcut_sym. This ensures the corresponding release event is ignored in the main mode, if the shortcut triggered a mode exit. For example, pressing Return in search mode would exit search mode, and then immediately reset the search match, if the kitty keyboard protocol mode with release events were enabled.
2024-07-23unicode-mode: disable debug loggingDaniel Eklöf-1/+1
2024-05-21unicode-mode: move state from seat to termDaniel Eklöf-26/+25
This fixes an issue where entering unicode-mode in one foot client, also enabled unicode-mode on other foot clients. Both visually (although glitchy), and in effect. The reason the state was originally in the seat objects, was to fully support multi-seat. That is, one seat/keyboard entering unicode-mode should not affect other seats/keyboards. The issue with this is that seat objects are Wayland global. Thus, in server mode, all seat objects are shared between the foot clients. There is a similarity with IME, which also keeps state in the seat. There's one big difference, however, and that is IME has Wayland native enter/leave events, that the compositor emits when windows are focused/unfocused. These events allow us to reset IME state. For our own Unicode mode, there is nothing similar. This patch moves the Unicode state from seats, to the terminal struct. This does mean that if one seat/keyboard enters Unicode mode, then *all* seats/keyboards will affect the unicode state. This potential downside is outweighed by the fact that different foot clients no longer affect each other. Closes #1717
2024-01-03support numpad in unicode modeSivecano-0/+2
2022-07-29unicode-mode: ‘q’ aborts Unicode input modeDaniel Eklöf-0/+1
2022-07-29unicode-input: move input (key press) handling to unicode_mode_input()Daniel Eklöf-0/+67
2022-07-29input: add new Unicode input modeDaniel Eklöf-0/+38
This mode is activated through the new key-bindings.unicode-input and search-bindings.unicode-input key bindings. When active, the user can “build” a Unicode codepoint by typing its hexadecimal value. Note that there’s no visual feedback in this mode. This is intentional. This mode is intended to be a fallback for users that don’t use an IME. Closes #1116
2020-10-10selection: use appropriate check for PRIMARY pasteSergey Nazaryev-110/+0
Assume it could be a copy-paste typo. We should check PRIMARY, not CLIPBOARD. Without this fix, we can't use PRIMARY until we copy anything to CLIPBOARD.