Dual screen setup with (dual-screen) workspace swithching
Hi, I am quite new to xmonad, but I find it quite useful :D (compared to my window-dragging coworkers, who don't see the sense :D) The story is: I have a working dual-screen setup, where each screen is a workspace. This is probably the most default way to have it... My problem is, that I mostly work with apps that produce a lot of windows. This is the first reason why I have dual-screen setup after all... So I arrange nicely all the windows on the two screens (say [1] and [2]), but I also work with multiple instances of the application. That means I have another application (with similarly-looking windows) on screens [2] and [3]. And another on [4][5]. And another.... Now here's the catch: When I want to switch to the other project (2,3) i need to change BOTH workspaces (say: mod-w,mod-3, mod-e,mod-4). Then to go back the procedure repeats. This is annoying... It is even more annoying if I forget on which dual-workspaces my apps were, and I mess instance 1 with instance 2 (say have workspaces [1] and [4]). Then my app responds in silly way (of course) and I don't see why... So the question is: Is it possible to have a setup with 'dual-screen,dual-sub-workspace' workspaces? So to have [1][2] merged in [super1] and [3][4] merged into [super2] ? So when I switch to [super1] i get [1][2], and so on... It could be that [1][2] is merged into a big [1] (but preserving the mod-w,mod-e functionality!! That's a must!), so that (mod-shift-1) would move some other window to that workspace... I don't mind that it would end up in either say [1a] or [1b], that I can manage later ;) Thanks and regards, Kuba
Hi, you might want to have a look at: http://code.google.com/p/xmonad/issues/detail?id=432 it's a module for linking workspaces... for a more basic solution you might just rebind your mod+# stuff in a way that you just execute view 1 on screen 1 and view 2 on screen two using onScreen from independent screens. Regards, Jan On Thu, Mar 24, 2011 at 09:56:18AM +0100, Kuba wrote:
Hi,
I am quite new to xmonad, but I find it quite useful :D (compared to my window-dragging coworkers, who don't see the sense :D)
The story is: I have a working dual-screen setup, where each screen is a workspace. This is probably the most default way to have it...
My problem is, that I mostly work with apps that produce a lot of windows. This is the first reason why I have dual-screen setup after all... So I arrange nicely all the windows on the two screens (say [1] and [2]), but I also work with multiple instances of the application. That means I have another application (with similarly-looking windows) on screens [2] and [3]. And another on [4][5]. And another.... Now here's the catch: When I want to switch to the other project (2,3) i need to change BOTH workspaces (say: mod-w,mod-3, mod-e,mod-4). Then to go back the procedure repeats.
This is annoying... It is even more annoying if I forget on which dual-workspaces my apps were, and I mess instance 1 with instance 2 (say have workspaces [1] and [4]). Then my app responds in silly way (of course) and I don't see why...
So the question is: Is it possible to have a setup with 'dual-screen,dual-sub-workspace' workspaces? So to have [1][2] merged in [super1] and [3][4] merged into [super2] ? So when I switch to [super1] i get [1][2], and so on...
It could be that [1][2] is merged into a big [1] (but preserving the mod-w,mod-e functionality!! That's a must!), so that (mod-shift-1) would move some other window to that workspace... I don't mind that it would end up in either say [1a] or [1b], that I can manage later ;)
Thanks and regards, Kuba
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad
-- Jan-David Quesel Carl von Ossietzky Universität Oldenburg Department of Computing Science Correct System Design D-26111 Oldenburg, Germany Phone: +49 (0)441 798-2376 Fax: +49 (0)441 798-2965
On Thu, Mar 24, 2011 at 09:56:18AM +0100, Kuba wrote:
Hi,
I am quite new to xmonad, but I find it quite useful :D (compared to my window-dragging coworkers, who don't see the sense :D)
The story is: I have a working dual-screen setup, where each screen is a workspace. This is probably the most default way to have it...
My problem is, that I mostly work with apps that produce a lot of windows. This is the first reason why I have dual-screen setup after all... So I arrange nicely all the windows on the two screens (say [1] and [2]), but I also work with multiple instances of the application. That means I have another application (with similarly-looking windows) on screens [2] and [3]. And another on [4][5]. And another.... Now here's the catch: When I want to switch to the other project (2,3) i need to change BOTH workspaces (say: mod-w,mod-3, mod-e,mod-4). Then to go back the procedure repeats.
If you are using the latest darcs version of xmonad-contrib (and if you are not, it's not that hard to switch and the development version is actually just as stable as the releases), you may be interested in the XMonad.Actions.DynamicWorkspaceGroups module. You can dynamically assign a name to groups of workspaces and then switch to the group by name. You could also set up some groups ahead of time in your config and have some keybinding to switch between them. -Brent
Hey,
uuuu this is exciting :) Indeed i have often 'sets' of project-related
workspaces, that could be it. I'll try
to follow the previous suggestion about linked workspaces I had to learn how
to download, patch and compile xmonad so it should be now in the newest
version.
BTW. I would never ever expect the compilation to work so easily! wow....
Regards,
Kuba
On Thu, Mar 24, 2011 at 4:18 PM, Brent Yorgey
On Thu, Mar 24, 2011 at 09:56:18AM +0100, Kuba wrote:
Hi,
I am quite new to xmonad, but I find it quite useful :D (compared to my window-dragging coworkers, who don't see the sense :D)
The story is: I have a working dual-screen setup, where each screen is a workspace. This is probably the most default way to have it...
My problem is, that I mostly work with apps that produce a lot of windows. This is the first reason why I have dual-screen setup after all... So I arrange nicely all the windows on the two screens (say [1] and [2]), but I also work with multiple instances of the application. That means I have another application (with similarly-looking windows) on screens [2] and [3]. And another on [4][5]. And another.... Now here's the catch: When I want to switch to the other project (2,3) i need to change BOTH workspaces (say: mod-w,mod-3, mod-e,mod-4). Then to go back the procedure repeats.
If you are using the latest darcs version of xmonad-contrib (and if you are not, it's not that hard to switch and the development version is actually just as stable as the releases), you may be interested in the XMonad.Actions.DynamicWorkspaceGroups module. You can dynamically assign a name to groups of workspaces and then switch to the group by name. You could also set up some groups ahead of time in your config and have some keybinding to switch between them.
-Brent
participants (3)
-
Brent Yorgey -
Jan-David Quesel -
Kuba