unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: 56117@debbugs.gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/","
Date: Fri, 24 Jun 2022 07:58:52 +0200	[thread overview]
Message-ID: <87v8sq1u1v.fsf@gmail.com> (raw)
In-Reply-To: <87bkujhf44.fsf@yahoo.com> (Po Lu via's message of "Thu, 23 Jun 2022 18:02:35 +0800")

(Taken off-list because I'd rather limit the noise; I'm very likely
missing something)

Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> And there's absolutely no way for Emacs to get at the original keys?
>
> It can by turning the input method off, but as a result any features
> provided by them will no longer work.

I'm a bit confused by that statement; you may remember that silly
experiment I ran in bug#52795?

https://debbugs.gnu.org/cgi/bugreport.cgi?att=1;msg=17;filename=goof.patch;bug=52795

Po Lu <luangruo@yahoo.com> writes:

> Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
>
>> AFAICT Emacs receives enough information to see S-SPC?
>
> Yes, but after going through an input method module the S-SPC is lost.
>
>> No idea how easy it would be to pass on that information to the rest
>> of Emacs.
>
> Not easy, if we want to keep input methods (which GTK uses to implement
> the compose key) working.

At the time that left me with the impression that in principle, Emacs
could record what it received before "going through an input method" and
recover the lost information after the input method did its (bad) job;
in practice I assume that would be a very horrible kludge and a
nightmare to maintain.

Was that impression correct?  I'm not pushing for such a kludge; just
wondering if it's in the realm of possibility.





  parent reply	other threads:[~2022-06-24  5:58 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
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 [this message]
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=87v8sq1u1v.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=56117@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).