i3 FAQ - Individual question feed

Using Windows systems in vnc or VM With windows key/super/mod4.

Fri, 17 Jan 2014 19:45:57 +0000

I use VNC, and Windows Virtual Machines on a regular basis. This causes issues when using mod4/super as the mod key. Are there any recommendations for what mod key/key combination to use so that I am not doing funky stuff in windows while trying to use i3 key bindings? Example: I have my mod key set to super, so mod+1 switch to 'workspace 1'... as it should... If I am on a VNC window, and I do this, it opens the start menu on the VNC machine, and then switches to 'workspace 1' (leaving the start menu open.) to get around this, I open another window in the same workspace as the VNC window (Usually urxvt) click on it, then I am free to use the super key with out messing with windows.

Comment by joepd for
I use VNC, and Windows Virtual Machines on a regular basis. This causes issues when using mod4/super as the mod key.

Are there any recommendations for what mod key/key combination to use so that I am not doing funky stuff in windows while trying to use i3 key bindings?

Example: I have my mod key set to super, so mod+1 switch to 'workspace 1'... as it should... If I am on a VNC window, and I do this, it opens the start menu on the VNC machine, and then switches to 'workspace 1' (leaving the start menu open.)

to get around this, I open another window in the same workspace as the VNC window (Usually urxvt) click on it, then I am free to use the super key with out messing with windows.

Thu, 23 Jan 2014 23:26:05 +0000

An alternative workaround: You can click on i3bar to get $mod back. I am interested in a real answer as well.

Comment by debugrr for
I use VNC, and Windows Virtual Machines on a regular basis. This causes issues when using mod4/super as the mod key.

Are there any recommendations for what mod key/key combination to use so that I am not doing funky stuff in windows while trying to use i3 key bindings?

Example: I have my mod key set to super, so mod+1 switch to 'workspace 1'... as it should... If I am on a VNC window, and I do this, it opens the start menu on the VNC machine, and then switches to 'workspace 1' (leaving the start menu open.)

to get around this, I open another window in the same workspace as the VNC window (Usually urxvt) click on it, then I am free to use the super key with out messing with windows.

Fri, 24 Jan 2014 02:57:56 +0000

That does work… guess I will unhide my i3bar, for the work around. Still doesn't solve the issue completely though.

Comment by debugrr for
I use VNC, and Windows Virtual Machines on a regular basis. This causes issues when using mod4/super as the mod key.

Are there any recommendations for what mod key/key combination to use so that I am not doing funky stuff in windows while trying to use i3 key bindings?

Example: I have my mod key set to super, so mod+1 switch to 'workspace 1'... as it should... If I am on a VNC window, and I do this, it opens the start menu on the VNC machine, and then switches to 'workspace 1' (leaving the start menu open.)

to get around this, I open another window in the same workspace as the VNC window (Usually urxvt) click on it, then I am free to use the super key with out messing with windows.

Tue, 28 Jan 2014 19:47:41 +0000

experimenting with a 'VNC mode' for particular workspaces. -- basically, When moving to a 'VNC' or 'VM' workspace, it swaps the mod key from super --> to [something else] while in the mode, then when you move out it switches to 'regular/clean' mode.... but it seems messy and clunky to say the least.

Answer by debugrr for
I use VNC, and Windows Virtual Machines on a regular basis. This causes issues when using mod4/super as the mod key.

Are there any recommendations for what mod key/key combination to use so that I am not doing funky stuff in windows while trying to use i3 key bindings?

Example: I have my mod key set to super, so mod+1 switch to 'workspace 1'... as it should... If I am on a VNC window, and I do this, it opens the start menu on the VNC machine, and then switches to 'workspace 1' (leaving the start menu open.)

to get around this, I open another window in the same workspace as the VNC window (Usually urxvt) click on it, then I am free to use the super key with out messing with windows.

Wed, 05 Feb 2014 03:00:26 +0000

I ended up mapping my 'Capslock' button to be Hyper_L and setting it to Mod3. This works because I don't use 'Capslock' and don't have an actual Hyper_L button and windows doesn't use it. Not sure how much I like it... but it works... (xmodmap output below.)

shift       Shift_L (0x32),  Shift_R (0x3e)
lock      
control     Control_L (0x25),  Control_R (0x69)
mod1        Alt_L (0x40),  Alt_R (0x6c),  Meta_L (0xcd)
mod2        Num_Lock (0x4d)
mod3        Hyper_L (0x42),  Hyper_L (0xcf)
mod4        Super_L (0x85),  Super_R (0x86),  Super_L (0xce)
mod5        ISO_Level3_Shift (0x5c),  Mode_switch (0xcb)



Answer by BatmanAoD for I use VNC, and Windows Virtual Machines on a regular basis.
This causes issues when using mod4/super as the mod key.

Are there any recommendations for what mod key/key combination to use so that I am not doing funky stuff in windows while trying to use i3 key bindings?

Example: 
I have my mod key set to super, so mod+1 switch to 'workspace 1'... as it should...
If I am on a VNC window, and I do this, it opens the start menu on the VNC machine, and then switches to 'workspace 1' (leaving the start menu open.)

to get around this, I open another window in the same workspace as the VNC window (Usually urxvt) click on it, then I am free to use the super key with out messing with windows.
Thu, 06 Feb 2014 18:37:55 +0000
You should be able to disable all of the Windows shortcuts that use the Windows key; this way you won't have a conflict. I think this is the way to do it: http://support.microsoft.com/kb/216893

I happen to use Win-L to lock my PC on a regular basis, and unfortunately it appears that there's no easy way to lock it if this is not enabled, so I keep this one shortcut enabled. I use Vim-like movement keys (`hjkl` instead of `jkl;`), so this means that moving my focus to the right causes the PC to lock. To avoid this, I have made a duplicate mapping of Win-o to also move focus right.


Comment by BatmanAoD for You should be able to disable all of the Windows shortcuts that use the Windows key; this way you won't have a conflict. I think this is the way to do it: http://support.microsoft.com/kb/216893

I happen to use Win-L to lock my PC on a regular basis, and unfortunately it appears that there's no easy way to lock it if this is not enabled, so I keep this one shortcut enabled. I use Vim-like movement keys (hjkl instead of jkl;), so this means that moving my focus to the right causes the PC to lock. To avoid this, I have made a duplicate mapping of Win-o to also move focus right.
Thu, 06 Feb 2014 19:00:32 +0000
Oh, in that case that's definitely a better solution.


Comment by debugrr for You should be able to disable all of the Windows shortcuts that use the Windows key; this way you won't have a conflict. I think this is the way to do it: http://support.microsoft.com/kb/216893

I happen to use Win-L to lock my PC on a regular basis, and unfortunately it appears that there's no easy way to lock it if this is not enabled, so I keep this one shortcut enabled. I use Vim-like movement keys (hjkl instead of jkl;), so this means that moving my focus to the right causes the PC to lock. To avoid this, I have made a duplicate mapping of Win-o to also move focus right.
Thu, 06 Feb 2014 18:51:25 +0000
i do support on a couple hundred machines, so changing the shortcuts on all of them is not going to happen.

I just switched my mod key, was the simpler solution.