You are not logged in.
All the key bindings I have in my config file work just fine except one....
$mod+Shift+2
This should move the current container to workspace 2 but it does nothing.
I'm using an IBM model M with caps-lock as the super key. I thought it might be the keyboard itself so I swapped it for a different model M but the problem persists.
If I plug in a regular keyboard with a windows key, the caps-lock no longer functions as the super key but the windows key does work.
I've tried using xev to try and nab the keycode but no code is generated for the caps-lock+shift+2 key combo.
Needless to say, I'm confused.
Last edited by taintedsushi (2021-06-15 13:46:10)
Offline
If there's a passive grab on the shortcut, you won't get the event in xev (but only a keymap notification and a focus change)
shift+2 rings… something.
What keyboard layout do you use and how do you set it?
Offline
I'm using the standard PC104 US layout I believe. I change caps-lock to super using .Xmodmap :
clear Lock
keycode 66 = Hyper_L
Interestingly, this works :
bindsym $mod+Ctrl+2 move container to workspace $ws2
But this doesn't:
bindsym $mod+Shift+2 move container to workspace $ws2; workspace $ws2
Offline
I believe
setxkbmap -print -query
Can you bind $mod+@ or $mod+shift+@ ?
Offline
Output from setxkbmap -print -query:
map {
};
rules: evdev
layout: us
Neither $mod+@ or $mod+shift+@ work.
Maybe this has something to do with it being a Model-m?
Offline
If you don't bind the shortcut, do you get an event in xev?
Offline