-
Hi, I would like to use However, on this keyboard a few ASCII characters are only available as Option+key combinations to make room for our beloved umlauts.
This works fine for all of them, except for the backslash (option+shift+7). This doesn't seem to happen with other option+shift+number combinations, only 7 and 0. Any idea what's going on here? I checked the keyboard tab in Terminal Inspector, the key sequences don't look any different to other option+shift+number combinations. Is there a way to make this mapping work? My current workaround is to remap only the right option key to alt. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi, I have the exact same issue on my Swedish keyboard. Bindings for alt+{7,8,9} works, as well as shift+alt+{8,9}. But specifically shift+alt+7 does not work. It does not seem to be related to text:\\, if I change it to text:X it does not work either. According to hexdump, it looks like the key outputs hex 1b 2f (ESC /) instead of the bound key.
In the keyboard inspector, shift+alt+8 generates "Press: Shift+Alt+eight; Release Shift+Alt+eight", while shift+alt+7 generates "Press: Shift+Alt+slash; Release Shift+Alt+seven". I.e. with 7, the press and release events are mismatched. Maybe this is a hint to solve the issue. As a workaround, the following keybind seems to work:
|
Beta Was this translation helpful? Give feedback.
Hi, I have the exact same issue on my Swedish keyboard. Bindings for alt+{7,8,9} works, as well as shift+alt+{8,9}. But specifically shift+alt+7 does not work. It does not seem to be related to text:\\, if I change it to text:X it does not work either. According to hexdump, it looks like the key outputs hex 1b 2f (ESC /) instead of the bound key.
In the keyboard inspector, shift+alt+8 generates "Press: Shift+Alt+eight; Release Shift+Alt+eight", while shift+alt+7…