We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am using caps_word which is working for all keys except for the ones with German umlauts:
ö - Ö (SEMICOLON) ä - Ä (SINGLE_QUOTE) ü - Ü (LEFT_BRACKET)
They are defined in my keymap as normal keypresses like this:
"value": "&kp", "params": [ { "value": "SEMICOLON", "params": [] } ]
I also had the problem that my continue-list did not work for them but I found out that it works by using the long name instead of the short one.
SEMI -> SEMICOLON SQT -> SINGLE_QUOTE LBKT -> LEFT_BRACKET
But the caps_word still doesn't work with the full names. It continues writing the lower case versions for the umlauts when the caps_word is enabled.
ZMK version: bb48661
The text was updated successfully, but these errors were encountered:
replace 'short names' with 'long names' for German umlauts keycodes (…
cfcaf6d
…see also: zmkfirmware/zmk#2807)
#1742 would provide a way to fix this.
Sorry, something went wrong.
No branches or pull requests
I am using caps_word which is working for all keys except for the ones with German umlauts:
ö - Ö (SEMICOLON)
ä - Ä (SINGLE_QUOTE)
ü - Ü (LEFT_BRACKET)
They are defined in my keymap as normal keypresses like this:
"value": "&kp", "params": [ { "value": "SEMICOLON", "params": [] } ]
I also had the problem that my continue-list did not work for them but I found out that it works by using the long name instead of the short one.
SEMI -> SEMICOLON
SQT -> SINGLE_QUOTE
LBKT -> LEFT_BRACKET
But the caps_word still doesn't work with the full names. It continues writing the lower case versions for the umlauts when the caps_word is enabled.
ZMK version: bb48661
The text was updated successfully, but these errors were encountered: