4 ms·

Hmm, so what is it about Xmonad that you like exactly? Reading the FAQ I see this: > When xmonad starts, workspace 1 is on screen 1, workspace 2 is on screen 2

Hmm, so what is it about Xmonad that you like exactly? Reading the FAQ I see this: > When xmonad starts, workspace 1 is on screen 1, workspace 2 is on screen 2, etc. When switching workspaces to one that is already visible, the current and visible workspaces are swapped. I actually like how Awesome does things but I can see how it might be nice to have one set of screens. Though I feel like you could probably script the keybindings to achieve more or less that functionality yourself, it's really easy to mess around with that kind of thing in Lua. Personally I feel like usually since my monitors are of vastly different size (laptop vs external monitor) I actually prefer to have specific layouts on specific monitors.

freshhawk 12y ago
Actually this one is not an easily scriptable thing. I dove deep on this one. The main use case I miss is this one. I work with two monitors, either a 30" and a sideways 24" or a 30" and my laptop screen. Gvim, terminal windows, etc on the primary and web browser on the secondary. Works fine in xmonad and awesome. But then I have something unusual, maybe I have a screen with a mitm proxy and a detached chromium devtools or console and a repl all layed out nicely to debug something. Aha, I think I found it, let me look at the code ... shit, I layed these out on my primary. With xmonad I can throw that whole screen over to the secondary, might have to adjust a bit because of the resolution difference but that's way easier than having to move each app over individually which just completely breaks flow. I tried to script it but it just ends up a mess because you do have to move each application individually and they always require a lot of fiddling. Lua is very easy to mess around with, my first day with awesome I couldn't find a battery monitor that I liked and that worked with my laptop so I just wrote one that's perfect. Took about 2 hours since I had never written Lua before. The docs were quite good. Xmonad should take note, have some actual documentation. Auto-generated garbage consisting solely of type signatures doesn't count.

freshhawk 12y ago

Actually this one is not an easily scriptable thing. I dove deep on this one. The main use case I miss is this one. I work with two monitors, either a 30" and a sideways 24" or a 30" and my laptop screen. Gvim, terminal windows, etc on the primary and web browser on the secondary. Works fine in xmonad and awesome. But then I have something unusual, maybe I have a screen with a mitm proxy and a detached chromium devtools or console and a repl all layed out nicely to debug something. Aha, I think I found it, let me look at the code ... shit, I layed these out on my primary. With xmonad I can throw that whole screen over to the secondary, might have to adjust a bit because of the resolution difference but that's way easier than having to move each app over individually which just completely breaks flow. I tried to script it but it just ends up a mess because you do have to move each application individually and they always require a lot of fiddling. Lua is very easy to mess around with, my first day with awesome I couldn't find a battery monitor that I liked and that worked with my laptop so I just wrote one that's perfect. Took about 2 hours since I had never written Lua before. The docs were quite good. Xmonad should take note, have some actual documentation. Auto-generated garbage consisting solely of type signatures doesn't count.