Thanks for the answers, I will check what Brandon mentioned. On Wed, Feb 1, 2017 at 10:16 PM, Brandon Allbery wrote:

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_greedyView_with_view

On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar wrote:

...

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

Can you show the config you tried after following the greedyView FAQ? That really should fix the behavior you're describing. The second feature you describe can *also* be done, see: http://hackage.haskell.org/package/xmonad-contrib-0.12/docs/XMonad-Layout-In... ~d On Wed, Feb 1, 2017 at 9:57 PM, Lajos Bodnar wrote:

Hi! Morning :) I tried what Brandon mentioned before, but the result is same. Did you send me a correct link about a correct xmonad.hs ? Maybe can I make a configuration where the half of the workspaces resides the screen 1 and the other ones resides screen 2 ?

Regards, Lajos

On Wed, Feb 1, 2017 at 10:27 PM, Lajos Bodnar wrote:

...

Thanks for the answers, I will check what Brandon mentioned.

On Wed, Feb 1, 2017 at 10:16 PM, Brandon Allbery wrote:

...

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_greedyView_with_view

On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar wrote:

...

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

_______________________________________________ xmonad mailing list xmonad@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad

Hi! Daniel, I tried the "IndependentScreens" and it's working like a charm. Thanks for all to all of you :) On Thu, Feb 2, 2017 at 8:17 AM, Lajos Bodnar wrote:

Hi Daniel. I'm in my workplace and I will look at it home.

thanks Lajos

On Thu, Feb 2, 2017 at 7:24 AM, Daniel Wagner wrote:

...

Can you show the config you tried after following the greedyView FAQ? That really should fix the behavior you're describing.

The second feature you describe can *also* be done, see: http://hackage.haskell.org/package/xmonad-contrib-0.12/docs/ XMonad-Layout-IndependentScreens.html

~d

On Wed, Feb 1, 2017 at 9:57 PM, Lajos Bodnar wrote:

...

Hi! Morning :) I tried what Brandon mentioned before, but the result is same. Did you send me a correct link about a correct xmonad.hs ? Maybe can I make a configuration where the half of the workspaces resides the screen 1 and the other ones resides screen 2 ?

Regards, Lajos

On Wed, Feb 1, 2017 at 10:27 PM, Lajos Bodnar wrote:

...

Thanks for the answers, I will check what Brandon mentioned.

On Wed, Feb 1, 2017 at 10:16 PM, Brandon Allbery wrote:

...

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_greedyView_with_view

On Wed, Feb 1, 2017 at 12:36 PM, Lajos Bodnar

...

wrote:

...

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

_______________________________________________ xmonad mailing list xmonad@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad

_______________________________________________ xmonad mailing list xmonad@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad