unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Thomas Schneider <qsx@chaotikum.eu>
Cc: 56117@debbugs.gnu.org
Subject: bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/","
Date: Tue, 21 Jun 2022 10:00:28 +0800	[thread overview]
Message-ID: <87y1xqkc77.fsf@yahoo.com> (raw)
In-Reply-To: <wwuk09bx7jq.fsf@chaotikum.eu> (Thomas Schneider's message of "Tue, 21 Jun 2022 01:02:33 +0200")

Thomas Schneider <qsx@chaotikum.eu> writes:

> Dear maintainers,
>
> With “classic” X11 support in Emacs and GTK (probably the others, too),
> pressing the keypad separator ("," on, e.g., a german keyboard layout,
> "." on most others), gave emacs the key <kp-separator>.  With pgtk, this
> is no longer the case.

This is a known problem with several GTK input methods.  There is
nothing we can do.  You can disable using the GTK input method system by
running (pgtk-use-im-context nil), but quite obviously input methods and
the compose key will no longer work.

If you are using X Windows, this, along with many other problems, is why
you should not be using the PGTK port.  Contrary to popular belief, the
"classic" X support is not slower than the PGTK port (in fact, it is
often faster), and has much better support for the X window system,
including features that are simply absent on PGTK, such as support for
drag-and-drop.





  reply	other threads:[~2022-06-21  2:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 23:02 bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/"," Thomas Schneider
2022-06-21  2:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-22 20:44   ` Stefan Kangas
2022-06-23  0:44     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-23  7:51       ` Lars Ingebrigtsen
2022-06-23  8:16         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-23  8:28           ` Eli Zaretskii
2022-06-23  8:40             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-23  9:49               ` Eli Zaretskii
2022-06-23 10:02                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-23 10:19                   ` Eli Zaretskii
2022-06-23 11:37                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-23 13:00                       ` Eli Zaretskii
2022-06-24  5:58                   ` Kévin Le Gouguec
2022-06-24 16:43                     ` Kévin Le Gouguec

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=87y1xqkc77.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56117@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=qsx@chaotikum.eu \
    /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).