After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 663370 - Change keybinding for switching between workspaces
Change keybinding for switching between workspaces
Status: RESOLVED DUPLICATE of bug 689969
Product: gnome-shell
Classification: Core
Component: general
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-11-04 04:02 UTC by Age Bosma (IRC: Forage)
Modified: 2013-05-29 23:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Age Bosma (IRC: Forage) 2011-11-04 04:02:10 UTC
With GNOME-Shell, using multiple workspaces has gotten a more important role. The taskbar used to allow you to quickly call multiple applications to the front whereas the application overview now requires you to refocus multiple times to achieve the same. You would have to switch from normal view to overview for each application you would like to call to the front. The constant switching between viewing modes can be reduced by using multiple workspaces.

The change of the desktop when changing to and from overview mode is as drastic as when switching from workspaces. Both actions also apply to application handling.

Because of their similar impact, function and importance, I think switching workspaces should be made more accessible as well. I'd like to propose using the System+ARROW combination to switch between workspaces. It reduces the amount of finger stretching, decreases the chance of pressing a wrong key combination (miss-pressing) and it makes an easier keybinding to remember.
System+ARROW also makes more sense then the current CTRL+ALT+ARROW combination. Whereas the CTRL-ALT combination does not have a general meaning, the System key got a meaning now that it is used to call the overview, thus having the effect mentioned above.
Comment 1 Milan Bouchet-Valat 2011-12-04 19:28:33 UTC
Makes sense, but I'm not sure that would make the keybinding much easier to user/discover. The change should probably be part of a more general move toward new System+X bindings. And we need to think about generations of users accustomed to to old binding: do we need to keep the old version too? I'd say yes.
Comment 2 Florian Müllner 2011-12-04 19:33:45 UTC
(In reply to comment #1)
> do we need to keep the old version too? I'd say yes.

Note that when moving keybindings to GSettings, all bindings are now stored as lists, so having multiple default bindings is not only supported, but actually trivial.
Comment 3 ahatomastarday 2011-12-05 12:12:35 UTC
If I remember correctly, System + Arrow is the keybinding used to snap windows to the sides of the screen and maximize/minimize windows in Windows 7. There was some discussion here on Bugzilla about adopting the same keybindings for the same actions for the GNOME 3 desktop. I can't remember anybody opposing it. The implementation was posponed until keybindings were moved to GSettings, though. So we should keep this in mind, I think. Can't look for the actual bug right now, might do it later and perhaps we should mark it as related to this one.
Comment 4 ahatomastarday 2011-12-05 21:25:54 UTC
This was the bug report I was talking about before: https://bugzilla.gnome.org/show_bug.cgi?id=648700
Comment 5 Florian Müllner 2013-05-29 23:20:07 UTC
In 3.8, the new defaults are <super>PgUp/PgDown.

*** This bug has been marked as a duplicate of bug 689969 ***