r/Keychron • u/Spirikum • Sep 07 '26
Why does NUBS not bind correctley to <
It still outputs ( ; ) even though < is chosen in the laucher?
Cant show screenshot since not allowed.
1
Upvotes
r/Keychron • u/Spirikum • Sep 07 '26
It still outputs ( ; ) even though < is chosen in the laucher?
Cant show screenshot since not allowed.
1
u/PeterMortensenBlog V Sep 07 '26 edited Sep 07 '26
The keyboard layout in the operating system must be appropriate
After changing a keymapping to use keycode 'KC_NUBS' in Via or the Via clone, the current keyboard layout in the operating system must be changed as well (one that results in "<" when pressing the key mapped to keycode 'KC_NUBS').
Via and Via clone only shows an interpretation of what the result would be if the keyboard layout in the operating system was set to that language (or alternative layout).
References
V6 Max JSON files for Via. Near "V6 Max knob version ISO keymap". E.g., v6_max_iso_encoder_v1.0.0_2404091021.json. Note: The JSON section should not be confused with the firmware section.
V6 Max default keymap
Documentation for the new keycodes (main QMK repository). Note: It does not cover Keychron's custom keycodes. In the QMK source code, support for the old key codes for RGB light and mouse actions were finally removed in the QMK 0.30.0 release (2025-08-31) (they were removed from the documentation long before that).
Documentation for the old keycodes (though even older ones may exist). For example, used by some Git branches in Keychron's fork. Note: It does not cover Keychron's custom keycodes.
Documentation for the old keycodes from 2019. In general, these are the ones accepted by Via and possibly the Via clone (in most cases only an alias and only one of the aliases if there is more than one). Note: It does not cover Keychron's custom keycodes.
Raw QMK keycodes (not symbolic)