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 652104 - No option to use Qwerty hotkeys in alternative Latin keyboard layouts
No option to use Qwerty hotkeys in alternative Latin keyboard layouts
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkMenu
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-06-08 11:22 UTC by Josh Brown
Modified: 2018-02-10 03:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Josh Brown 2011-06-08 11:22:48 UTC
Some users prefer to use an alternative Latin layout such as Dvorak to increase their typing speed. Many of these users prefer to use the original Qwerty keyboard shortcuts which are conveniently positioned (e.g. Ctrl: C-Copy, V-Paste, S-Save). An option should be provided to use Qwerty hotkeys with alternative layouts.

Qwerty hotkeys are already used in the terminal and in non-latin keyboard layouts. Qwerty hotkeys were used in all keyboard layouts before bug 162726 was fixed.
Comment 1 Karl 2011-06-27 15:16:53 UTC
See my comments at Bug 162726.  Until it actually does get fixed, the following procedure will do what you want it to do, I think:

1. Set the default layout to US/standard
2. Set US/Dvorak as an alternative layout
3. When you first log in, immediately change layouts to US/Dvorak by clicking the layout switcher.  Your CTRL and ALT keys should still be mapped to US/standard, but your unmodified keys should point to the Dvorak map.

The only annoyance is that you'd have to remember to switch every time upon login.

Note that I consider this behavior a bug, which is exactly why I insist the first bug (#162726) be re-opened.  It is, however, a workaround for the time being.
Comment 2 Matthias Clasen 2018-02-10 03:29:24 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.