mod4.

asked 2014-01-17 19:45:57 +0000

21 ●1 ●1 ●5

updated 2014-01-17 20:12:19 +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.

edit retag flag offensive close merge delete

Comments

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

joepd ( 2014-01-23 23:26:05 +0000 )edit

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

debugrr ( 2014-01-24 02:57:56 +0000 )edit

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.

debugrr ( 2014-01-28 19:47:41 +0000 )edit

add a comment

2 answers

Sort by » oldest newest most voted

answered 2014-02-06 18:37:55 +0000

BatmanAoD
57 ●6 ●7 ●13

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.

edit flag offensive delete link

Comments

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.

debugrr ( 2014-02-06 18:51:25 +0000 )edit

Oh, in that case that's definitely a better solution.

BatmanAoD ( 2014-02-06 19:00:32 +0000 )edit

add a comment

answered 2014-02-05 03:00:26 +0000

debugrr

21 ●1 ●1 ●5

I ended up mapping my 'Capslock' button to be HyperL and setting it to Mod3. This works because I don't use 'Capslock' and don't have an actual HyperL button and windows doesn't use it.

Not sure how much I like it... but it works...

(xmodmap output below.)

shift       ShiftL (0x32),  ShiftR (0x3e)
lock 

control     ControlL (0x25),  ControlR (0x69)
mod1        AltL (0x40),  AltR (0x6c),  MetaL (0xcd)
mod2        NumLock (0x4d)
mod3        HyperL (0x42),  HyperL (0xcf)
mod4        SuperL (0x85),  SuperR (0x86),  SuperL (0xce)
mod5        ISOLevel3Shift (0x5c),  Modeswitch (0xcb)

edit flag offensive delete link

add a comment

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

Comments

2 answers

Comments

Question Tools

Stats

Related questions