From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Campbell Barton <ideasman42@gmail.com>
Cc: 53200@debbugs.gnu.org
Subject: bug#53200: 29.0.50; C-S-u shortcut fails with 'PGTK' enable
Date: Wed, 12 Jan 2022 14:24:35 +0800 [thread overview]
Message-ID: <87r19dsc7w.fsf@yahoo.com> (raw)
In-Reply-To: <CAEcf3Ny9UXvoeNxrbUg0vn2-0wJZj+MGM1KLQXdTGOxRQgOm8A@mail.gmail.com> (Campbell Barton's message of "Wed, 12 Jan 2022 15:56:03 +1100")
Campbell Barton <ideasman42@gmail.com> writes:
> With PGTK enabled (--with-pgtk) the following occurs:
>
> - Press C-S-u
> - Press a
>
> The character 'a' is entered.
>
> Without PGTK enabled, the following occurs:
>
> - Press C-S-u
> - Press a
>
> The character 'aaaa' is entered 4x.
>
> Note that PGTK seems to swallow this binding, since it's not possible to
> check what the shortcut does by pressing:
>
> C-H, K, C-S-u
>
> Which reports without PGTK: (universal-argument)
This has been reported at least twice already. Someone should volunteer
to find and merge all those bugs, but in short: most GTK input method
modules stupidly eat the shift modifier, and the only workaround is to
disable the use of GTK input methods by setting `pgtk-use-im-context' to
nil.
This is really a bug in the various input modules and should be reported
to their developers instead instead. If you're using ibus, for example,
complain to ibus developers about their IM context not setting the shift
modifier mask in an event sent by the filter.
Alternatively, you can use the regular X build, which is a much superior
experience over the PGTK port as long as you're not using Wayland.
Thanks, and please let us know about the progress of your complaining to
the IM module developers. It would be greatly appreciated.
next prev parent reply other threads:[~2022-01-12 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 4:56 bug#53200: 29.0.50; C-S-u shortcut fails with 'PGTK' enable Campbell Barton
2022-01-12 6:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-13 7:08 ` Lars Ingebrigtsen
2022-01-13 8:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-15 2:01 ` Morgan Smith
2022-05-22 16:25 ` daanturo
2022-05-22 17:44 ` Morgan Smith
2022-05-23 0:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87r19dsc7w.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=53200@debbugs.gnu.org \
--cc=ideasman42@gmail.com \
--cc=luangruo@yahoo.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).