From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 55660@debbugs.gnu.org, derek_upham@mailfence.com
Subject: bug#55660: 29.0.50; PGTK degrades to terminal-compatible keyboard events
Date: Fri, 27 May 2022 08:53:57 +0300 [thread overview]
Message-ID: <83ee0fo70q.fsf@gnu.org> (raw)
In-Reply-To: <87v8trivlc.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
merge 55660 53200
thanks
> Cc: 55660@debbugs.gnu.org
> Date: Fri, 27 May 2022 09:59:43 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Derek Upham <derek_upham@mailfence.com> writes:
>
> > Calling that function restores normal rich events.
> >
> > I’m using Ubuntu 20.04. The distro installs ibus-gtk3 as part of the
> > normal desktop experience, but I haven’t configured it. “im-config”
> > reports that it’s using the default en_US locale.
>
> Then this is a duplicate of bug#53200 (and many other similar issues).
> Would someone please merge the two?
Done (and anyone can easily do that).
Should this issue be in PROBLEMS?
next prev parent reply other threads:[~2022-05-27 5: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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ee0fo70q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55660@debbugs.gnu.org \
--cc=derek_upham@mailfence.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.