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 691549 - Add shortcut to "Move window to display on left/right/top/bottom"
Add shortcut to "Move window to display on left/right/top/bottom"
Status: RESOLVED DUPLICATE of bug 671054
Product: mutter
Classification: Core
Component: general
3.8.x
Other Linux
: Normal enhancement
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-01-11 13:39 UTC by Pieter Ennes
Modified: 2014-02-13 21:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Pieter Ennes 2013-01-11 13:39:47 UTC 
I love the "View split on left/right" shortcuts, but in dual screen mode you'd want to extend that function over both or all displays.

It would be great to have two new shortcuts

- View split next
- View split previous

that rotate the splits over all displays instead of just the current. You could bind these to the same keys as the existing left/right versions with the shift key added.
Comment 1 Pieter Ennes 2013-01-15 15:41:42 UTC 
Just occurred to me that instead of the above it may be simpler/better to add shortcuts to move a window across displays (not desktops) in general:

- Move window to display on "left/right/top/bottom"

Then you can first move it to the correct screen, after which it can be further positioned using the existing "View split on left/right" shortcuts if desired.
Comment 2 André Klapper 2013-08-09 03:26:12 UTC 
libgnomekbd is not used in GNOME 3.8. Reassigning.
Comment 3 Florian Müllner 2014-02-13 21:28:34 UTC 
(In reply to comment #1)
> Just occurred to me that instead of the above it may be simpler/better to add
> shortcuts to move a window across displays (not desktops) in general:
> 
> - Move window to display on "left/right/top/bottom"

We did that in bug 671054.

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