Skip to content

fix: parse function-key and enter bindings in config [bindings]#1689

Open
cantona wants to merge 2 commits into
raphamorim:mainfrom
cantona:fix/config-function-key-bindings
Open

fix: parse function-key and enter bindings in config [bindings]#1689
cantona wants to merge 2 commits into
raphamorim:mainfrom
cantona:fix/config-function-key-bindings

Conversation

@cantona

@cantona cantona commented Jun 25, 2026

Copy link
Copy Markdown

Function-key bindings in the [bindings] config silently did nothing. convert() (the config key parser) had no f1-f12, no enter alias (only return), and no backspace, so those keys hit the catch-all Err arm and the binding was dropped. For example:

[bindings]
keys = [{ key = "f11", action = "togglefullscreen" }]

did nothing — F11 fell through to the terminal as its escape sequence.

Add f1-f12, an enter alias, and backspace to convert(), matching the key set the hint-binding parser already accepts.

Standalone, based on main.

cantona and others added 2 commits June 25, 2026 18:54
convert() (the [bindings] config parser) had no f1-f12, no "enter"
alias (only "return"), and no "backspace", so those keys hit the
catch-all Err arm and the binding was silently dropped -- e.g.
`{ key = "f11", action = "togglefullscreen" }` did nothing and F11
fell through to the terminal. Add the function keys, an enter alias, and
backspace, matching the set the hint-binding parser already accepts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant