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 613396 - Metacity doesn't allow doing Alt + 7 on azerty keyboard
Metacity doesn't allow doing Alt + 7 on azerty keyboard
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: Focus
trunk
Other Linux
: Normal major
: ---
Assigned To: Thomas Thurman
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2010-03-20 11:03 UTC by Didier Roche
Modified: 2010-03-29 13:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Git format patch to revert default cycle_group keybinding (1.68 KB, patch)
2010-03-20 11:03 UTC, Didier Roche
committed Details | Review

Description Didier Roche 2010-03-20 11:03:08 UTC
Created attachment 156612 [details] [review]
Git format patch to revert default cycle_group keybinding

Looking at this commit:
http://git.gnome.org/browse/metacity/commit/?id=0f805bfdfb46e6739912df042f628ca9913b433c
the new default cycle_group keybinding to Alt-grave.

There are two wrong assumptions there:
- ` being above tab is surely true for some qwerty layout, but not in other layout like azerty (² is above the tab). We should find a clever way to find the key above tab
- ` is proceeded in azerty keyboard (french layout) by <Alt Gr + è>. The issue is that <Shift + è> is "7". And so, "Alt + 7" (used in some applications like irssi, weechat, …) is <Alt + Shift + è>, which is the reverse order to naviguate between grouped windows, and so, you can't anymore access to this keybinding.

Here is a simple patch reverting the change back to Alt + F6, which is I guess, less annoying. If I can help in the long term (some documentation pointer needed as I have not a strong background on keybindings) on the first mentioned point to get a better shortcut, I'll be happy to help there.
Comment 1 Vincent Untz 2010-03-29 13:27:04 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.