unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Derek Upham <derek_upham@mailfence.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 55660@debbugs.gnu.org
Subject: bug#55660: 29.0.50; PGTK degrades to terminal-compatible keyboard events
Date: Fri, 27 May 2022 08:53:35 -0700	[thread overview]
Message-ID: <87ee0fc6ps.fsf@priss.frightenedpiglet.com> (raw)
In-Reply-To: <87ee0fiewd.fsf@yahoo.com>


Po Lu <luangruo@yahoo.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Thanks, but shouldn't the heading line of the entry you added 
>> be
>> qualified with "in PGTK builds"? or maybe "in GTK and PGTK 
>> builds"?
>
> It's already under "Runtime problems specific to PGTK".

How about this?

** Keyboard behavior depends on your GTK input method

The GTK3 libraries may interpret and process keypresses as part of 
the
current GTK input method, before passing them as input events to 
Emacs.
GTK applications like PGTK Emacs configure their input method
automatically based on environment variables, particularly LANG 
and
GTK_IM_MODULE.

If you notice differences in keyboard behavior depending on how 
you
start PGTK Emacs, compare your environments using 
`process-environment'.
For example, you may see behavior differences when running Emacs 
out of
a systemd unit file, compared to running Emacs from the command 
line.
Input methods may also cause the keyboard behavior to change if 
you
switch from a GTK-based build to a PGTK-based build.

Emacs may reveal bugs that are in the input method libraries. 
Those
libraries are out of Emacs's control, but you can tell PGTK Emacs 
to
bypass input methods entirely using an Emacs Lisp function:

  M-: (pgtk-use-im-context nil)






  reply	other threads:[~2022-05-27 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 14:43 bug#55660: 29.0.50; PGTK degrades to terminal-compatible keyboard events Derek Upham
2022-05-27  0:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27  1:13   ` Derek Upham
2022-05-27  1:59     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27  5:53       ` Eli Zaretskii
2022-05-27  6:06         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27  7:07           ` Eli Zaretskii
2022-05-27  8:00             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 15:53               ` Derek Upham [this message]
2022-05-28  0:41                 ` 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=87ee0fc6ps.fsf@priss.frightenedpiglet.com \
    --to=derek_upham@mailfence.com \
    --cc=55660@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).