Hello, Before you dismiss this mail as another "read xrandr(1)" type, give me a chance to explain, please. Once again I'm on the quest to find a WM suiting my needs. So far, awesome works very well, the Lua API is quite usable and Shifty with dynamic tags is nearly exactly what I miss in other WMs (workpsace/group concept is too rigid and on-the-fly rename usually not included).
But then one day I try to plug in a monitor when I'm about to give a presentation. I prepared a special tag for it. Suddenly, all windows stuff up on one, new workspace (Shifty's fault). OK, but even if I retag my windows again, the new VGA screen has a different set of tags, so I cannot display my presentation on VGA and notes + presentation on laptop. I knew that Awesome restarts on screen geomtery change, but didn't comprehend such consequences. So, my problem may come from these two things: 1) If Awesome restarts on every screen change, what is the easiest way to conserve the current taglist(s) an respective layouts with Shifty? I can imagine that with vanilla Awesome I could put some if defined test for taglist, but even then I'm not sure if that would conserve the layouts. I would have to add another check for layouts too I guess. What I'm looking for is some reference implementation. I hope I won't have to fork Shifty and I'm just missing something. So far I haven't found anything useful, maybe most people use Awesome only in a static multi monitor setup. 2) Is it possible to share a tag pool among all screens? I've read through the Lua API code and it gave me an impression that it is assumed that each screen has it's own set of tags. So is it even possible to share a tag pool, or would many things break? No, xrandr --same-as is not the solution for me, because I may want e.g. to see tags 1,3,4 on one screen and 2,5 on another, because that is exactly why I prefer the tag concept over workspaces/groups. As side note, I also find the current implementation of setslave() rather flickery (not sure if due to the way it's in the default rc.lua or if it's the massive amount of swap() calls), has anybody had and solved such an issue ? I'm looking forward to any kind of suggestions, including those pointing me towards a different WM that could fit my needs better (not sure if dwm can share tags among screens). Thank you for this great project, Ondrej -- To unsubscribe, send mail to [email protected].
