From: Akira Kyle <akira@akirakyle.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Trey Peacock <gpg@treypeacock.com>,
Morgan Smith <morgan.j.smith@outlook.com>,
emacs-devel@gnu.org
Subject: Re: PGTK-related misconceptions
Date: Tue, 26 Jul 2022 15:36:15 -0600 [thread overview]
Message-ID: <87fsino7gd.fsf@akirakyle.com> (raw)
In-Reply-To: <875yjkzkuc.fsf@yahoo.com>
On Tue, Jul 26, 2022 at 10:08 AM, Po Lu <luangruo@yahoo.com>
wrote:
> It is to prevent errors when Mod4 is _not_ the super key. Very
> common
> on X (where Mod4 is commonly Hyper), and in fact it is caused by
> Mod4
> not being part of the Super virtual modifier in the compositor's
> XKB
> configuration.
>
> The conclusion I eventually came to is that the problem lies in
> the XKB
> configuration of the Wayland compositor in question (namely,
> Sway), and
> not Emacs nor GDK. It works with GNOME Shell and kwin because
> they set
> up their keyboards with the correct virtual modifiers by
> default. So
> what I'd recommend is to start an X server where the Super key
> does
> work, run:
>
> xkbcomp $DISPLAY name/of/xkb/file.xkb
>
> and then use that file with Sway.
This does not appear to work. I can attach the full .xkb file that
xkbcomp generated if you like, but it's the default which you get
from the following under the v2.34 xkeyboad-config files.
xkb_keymap "my_dvorak_super" {
xkb_keycodes { include "evdev" };
xkb_compatibility { include "complete" };
xkb_types { include "complete" };
xkb_symbols { include "us(dvorak)+pc(pc105)" };
};
Specifically, when I use the same .xkb file under X I get that
emacs interprets the physical keycode <RWIN> as Super whereas
under wayland with sway, emacs does not respond to <RWIN>. The
relevant lines from the xkb_symbols section are
key <RWIN> { [ Super_R ] };
modifier_map Mod4 { <RWIN> };
Reading through the links that Trey sent in previous emails to the
gtk source which handles modifier keys in x11 versus wayland, I'm
pretty convinced his diagnosis is correct. Namely gtk behaves
differently in stetting GDK_SUPER_MASK on x11 versus wayland where
on the former seeing the "Super_R" symbol will set the mask while
on the latter, only the virtual modifier "Super" will set
GDK_SUPER_MASK.
Although it seems like in principle, one should be able to get xkb
to set the "Super" virtual modifier so that GTK correctly picks it
up in it's wayland code. However thus far I have been unable to
make a set of xkb rules which will trigger the "Super" virtual
modifier for the <RWIN> keycode despite much effort. Perhaps this
is possible and I just don't understand xkb's rules sufficiently,
or perhaps there is some issue in xkb which is preventing from GTK
to picking up the "Super" virtual modifier. Thus far I have tried
many variations on some configuration like the following
default partial modifier_keys xkb_symbols "basic" {
include "us(dvorak)"
name[Group1] = "super";
key <RWIN> {
symbols[Group1]= [ Super_R ],
virtualMods= Super
};
key <LWIN> {
symbols[Group1]= [ Super_L ],
virtualMods= Super
};
};
What is also puzzling to me is that my .xkb file also includes the
"misc" xkb_compatibility rules which look like the following
interpret Super_R+Any {
virtualModifier= Super;
action = SetMods(modifiers=modMapMods);
};
interpret Super_R {
action = SetMods(modifiers=Super);
};
next prev parent reply other threads:[~2022-07-26 21:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 21:50 PGTK-related misconceptions Trey
2022-04-19 0:59 ` Po Lu
2022-04-19 3:28 ` Trey Peacock
2022-04-19 4:27 ` Po Lu
2022-04-19 23:02 ` Trey Peacock
2022-04-20 0:48 ` Po Lu
2022-04-20 2:33 ` Trey Peacock
2022-04-20 4:05 ` Po Lu
2022-07-25 21:18 ` Akira Kyle
2022-07-26 2:08 ` Po Lu
2022-07-26 12:10 ` Lars Ingebrigtsen
2022-07-26 12:35 ` Po Lu
2022-07-29 14:26 ` Stefan Monnier
2022-07-30 0:58 ` Po Lu
2022-07-26 21:36 ` Akira Kyle [this message]
2022-07-27 2:48 ` Po Lu
2022-07-27 8:34 ` Trey Peacock
2022-07-27 9:10 ` Po Lu
2022-07-27 13:45 ` Trey Peacock
2022-07-27 13:52 ` Po Lu
2022-07-28 1:39 ` Akira Kyle
2022-07-28 2:50 ` Po Lu
-- strict thread matches above, loose matches on Subject: below --
2022-04-20 7:52 Trey Peacock
2022-04-20 8:25 ` Po Lu
2022-04-20 13:13 ` Brian Cully
[not found] <DM5PR03MB3163BBCF9626AD3B88900011C5EE9@DM5PR03MB3163.namprd03.prod.outlook.com>
2022-04-15 2:29 ` Po Lu
2022-04-15 7:11 ` Byung-Hee HWANG
2022-04-15 16:24 ` Eric Abrahamsen
2022-04-18 5:18 ` Sean Whitton
2022-04-18 5:31 ` Po Lu
2022-04-18 5:43 ` Sean Whitton
2022-04-18 5:57 ` Po Lu
2022-04-18 18:27 ` Sean Whitton
2022-04-18 19:49 ` Jim Porter
2022-04-19 1:02 ` Po Lu
2022-04-19 2:46 ` Sean Whitton
2022-04-19 2:18 ` Tim Cross
2022-04-19 5:56 ` Eli Zaretskii
2022-04-19 8:13 ` Tim Cross
2022-04-19 10:32 ` Eli Zaretskii
2022-04-19 9:10 ` Dirk-Jan C. Binnema
2022-04-19 10:42 ` Po Lu
2022-04-19 11:53 ` Phil Sainty
2022-04-19 13:58 ` Sean Whitton
2022-04-20 3:29 ` Phil Sainty
2022-04-20 4:48 ` Stefan Monnier
2022-04-19 16:51 ` Yuri Khan
2022-04-22 5:44 ` Pankaj Jangid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsino7gd.fsf@akirakyle.com \
--to=akira@akirakyle.com \
--cc=emacs-devel@gnu.org \
--cc=gpg@treypeacock.com \
--cc=luangruo@yahoo.com \
--cc=morgan.j.smith@outlook.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).