GNOME Bugzilla – Bug 696350
"Move window one worskspace up" doesn't work if on first workspace
Last modified: 2015-03-07 06:42:24 UTC
It would be very nice to have it automatically create a new blank first workspace. Currently the workaround is to instead go into the overview, grab the window in question with the mouse and position it before the first workspace. Very slow!
Hey Hashem, what do you mean by "Move window one workspace up"? It sounds like an option from the window title menu, but that doesn't have the up item if you are in the top-most workspace.
I think the reporter, Hashem, was requesting that the first workspace not be fixed at the "top" of the list of workspaces when using the keyboard to move windows up and down workspaces. The keyboard is of special note here because this is already possible to do with the mouse. The manner of doing it with the mouse is to drag and hover a window above all of the existing workspaces, a hint will then appear that indicates the user may drop the window to create a workspace above the top one. No similar function exists for the keyboard, yet may still be expected from the CTRL+UP and CTRL+SHIFT+UP shortcuts. This feature could be very useful. In this way, a user could expand both up and down. This could allow fewer keystrokes to get to another workspace in use since workspaces could be managed both above and below the initial workspace, instead of only below. It may be easier to imagine this functionality as having the initial workspace be the middle workspace instead of the top one, while still hiding empty workspaces. Here is a use case: say a user prefers to have a only web browser open on the topmost workspace, but has many windows open on that workspace already. In order to achieve the setup where the browser is alone on the topmost workspace, the user needs to drag the window above the current workspace with the mouse. With this new functionality, given the same situation, the user could focus on the browser, hit CTRL+SHIFT+UP, and a new workspace would be created above the topmost workspace to accomodate the browser. Hopefully that helps, and ideally that's what Hashem was talking about, too.
Sorry, Allan I missed your request for more info. Nick, thanks for the explanation -- that is indeed what I had in mind. Good enough to remove NEEDINFO, Allan?
(In reply to comment #3) > Good enough to remove NEEDINFO, Allan? Yes.
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 665764 ***