From: Tassilo Horn <tsdh@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Tim Cross <theophilusx@gmail.com>,
emacs-devel@gnu.org, "T.V Raman" <raman@google.com>
Subject: Re: with-pgtk: C-; turns into plain ';'
Date: Wed, 16 Feb 2022 14:11:17 +0100 [thread overview]
Message-ID: <87a6erlzja.fsf@gnu.org> (raw)
In-Reply-To: <8735kjwa0f.fsf@yahoo.com>
Po Lu <luangruo@yahoo.com> writes:
>> If you were running the pgtk build and all the key bindings were
>> working fine and then suddenly they stopped working, I would agree it
>> it likely there is something more going on than simply "a known
>> problem with gtk and input methods".
>
> AFAICT, it's the same issue with "C-S-u" being reported as C-u on the
> PGTK port, which has been there since the beginning (search the bug
> tracker for more details.)
Interesting, I'm using pgtk on wayland/sway and C-h k C-S-u doesn't
report anything but inserts an underlined letter "u" in the current
buffer, even when that is read-only, and still seems to wait for my key.
Then, emacs is inresponsive, C-g won't work, and I need to switch to
another window and back again. At that point, the underlined u
disappears and I can interact with emacs again.
> Disabling input methods using `pgtk-use-im-context' makes both
> problems go away here for me, and none of that code has changed since
> it was installed.
When I run (pgtk-use-im-context nil), the above problem doesn't happen
and C-h k C-S-u reports C-u translated from C-S-u. However, I also
cannot insert characters like ` or ´ anymore. Pressing the relevant
AltGr-key combo on my German Dvorak layout doesn't seem to be received
by emacs. C-h k <AltGr-combo> doesn't receive anything.
So it seems like I can choose pest or cholera...
Bye,
Tassilo
next prev parent reply other threads:[~2022-02-16 13:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 3:43 with-pgtk: C-; turns into plain ';' T.V Raman
2022-02-15 4:49 ` Po Lu
2022-02-15 13:41 ` Eli Zaretskii
2022-02-15 13:45 ` Po Lu
2022-02-15 14:02 ` Eli Zaretskii
2022-02-15 14:03 ` Po Lu
2022-02-15 14:11 ` Eli Zaretskii
2022-02-16 0:03 ` Tim Cross
2022-02-16 0:48 ` Po Lu
2022-02-15 23:50 ` Tim Cross
2022-02-16 3:16 ` T.V Raman
2022-02-16 6:19 ` Tim Cross
2022-02-16 7:22 ` Po Lu
2022-02-16 13:11 ` Tassilo Horn [this message]
2022-02-16 13:37 ` Po Lu
2022-02-16 13:46 ` Tassilo Horn
2022-02-16 14:01 ` Po Lu
2022-02-16 17:48 ` Tassilo Horn
2022-02-17 0:43 ` Po Lu
2022-02-17 5:40 ` Tassilo Horn
2022-02-17 15:02 ` T.V Raman
2022-02-17 17:38 ` Tassilo Horn
2022-02-17 19:36 ` Eric Abrahamsen
2022-02-17 19:40 ` Eric Abrahamsen
2022-02-17 20:07 ` Tassilo Horn
2022-02-17 20:00 ` Tassilo Horn
2022-02-17 20:10 ` Eric Abrahamsen
2022-02-18 0:44 ` Po Lu
2022-02-18 3:13 ` T.V Raman
2022-02-18 3:25 ` Po Lu
2022-02-18 18:13 ` T.V Raman
2022-02-19 1:02 ` Po Lu
2022-02-19 8:00 ` Eli Zaretskii
2022-02-19 8:15 ` Po Lu
2022-02-19 15:23 ` T.V Raman
2022-02-20 1:01 ` Po Lu
2022-02-20 18:06 ` T.V Raman
2022-02-21 15:46 ` T.V Raman
2022-02-22 1:00 ` Po Lu
2022-02-18 0:42 ` Po Lu
2022-02-15 13:46 ` Dmitry Gutov
2022-02-15 13:48 ` Po Lu
2022-02-15 6:36 ` tomas
2022-02-15 11:56 ` Alan Mackenzie
2022-02-15 12:33 ` tomas
2022-02-16 0:13 ` Tim Cross
2022-02-15 13:08 ` Modifier keys on ttys (was: with-pgtk: C-; turns into plain ';') Stefan Monnier
2022-02-15 13:35 ` Alan Mackenzie
2022-02-15 14:19 ` Modifier keys on ttys Stefan Monnier
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=87a6erlzja.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=raman@google.com \
--cc=theophilusx@gmail.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).