You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. As of Lion, we are now given the ability to create and delete so-called
"Desktop Spaces" via Mission Control on-the-fly. This is a beautiful feature
that could be used to dedicate a location for csshX to work on.
2. Window management with 8+ hosts on your active desktop was always a
nightmare :). This is why --screen and --space were added, but 10.6's spaces
was terrible.
What is the expected output? What do you see instead?
I assume --space doesn't work under Lion, though I admit that I haven't used it
yet!
What version of csshX (do a "csshX -v") are you using? On what operating system
version?
csshX v0.73- (current SVN HEAD, r180) under 10.7 Lion
Please provide any additional information below.
Yep.
Original issue reported on code.google.com by vxjaso...@gmail.com on 12 Aug 2011 at 3:25
The text was updated successfully, but these errors were encountered:
I just confirmed that spaces support is very broken in 10.7. This is due to
changes in the undocumented API calls. I'll have to try and find some
workarounds, but I suspect it will take some time.
Original comment by gavin.brock on 16 Aug 2011 at 4:29
I unfortunately cannot be of any specific help, but I imagine that "numbered"
space may be gone. Whether they are or are not, as long as there is the ability
to manipulate Mission Control via scripting bridges, all hope is not lost. I
would love a --new-space flag I can pass to csshX to say "create a new Desktop
space and move your windows to it".
Having "--spaces #" correspond to any existing Desktop Space is still helpful,
if such a mechanism exists in the scripting bridges.
Original comment by vxjaso...@gmail.com on 16 Aug 2011 at 8:28
Original issue reported on code.google.com by
vxjaso...@gmail.com
on 12 Aug 2011 at 3:25The text was updated successfully, but these errors were encountered: