You don't need to add keybindings, they are default. I assume this means
you have been using the bad "example config" that overrides every possible
setting with the defaults from some particular version instead of
inheriting the defaults, and will need to be extremely careful about xmonad
upgrades because your config won't magically rewrite itself to be
compatible. (I think mod-shift-space is the one that will bite you in 0.13.)
I *think* you are talking about
https://wiki.haskell.org/Xmonad/Frequently_asked_questions#Replacing_greedyV...
On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar
Hi all. I'm new in the mail list, and sorry for my english ...
I tried to set up my wm for dual monitor with these keyboard settings: -- mod-[1..9], Switch to workspace N -- mod-shift-[1..9], Move client to workspace N -- [((m .|. mod4Mask, k), windows $ f i) | (i, k) <- zip (XMonad.workspaces conf) [xK_1 .. xK_9] , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]] ++ -- -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3 -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3 -- [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust (windows . f)) | (key, sc) <- zip [xK_w, xK_e] [0..] , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]]
I exprerienced that when I switch workspace the opened windows moved the new workspace from the inactive screen. If the inactive screen is empty in the workspace where I have just moved then a window will fill it. I hope it is understandable for you. Any idea ? What is wrong ? What causes it ?
Regards, Lajos
_______________________________________________ xmonad mailing list xmonad@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
-- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net