[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and
From: |
Eli Zaretskii |
Subject: |
bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/"," |
Date: |
Thu, 23 Jun 2022 11:28:39 +0300 |
> Cc: 56117@debbugs.gnu.org, stefan@marxist.se, qsx@chaotikum.eu
> Date: Thu, 23 Jun 2022 16:16:41 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > And as both Eli and I have said, we think those changes you've made to
> > pgtk here should be reverted so that these keys work as before.
>
> This isn't the super-key related bug, and in fact they shouldn't have
> been merged. No amount of changes on our side can work around input
> methods swallowing the shift modifier in "C-S-u" and the "kp-" in
> "kp-separator".
Maybe we are talking about an issue that is not understood well enough
by some participants (e.g., myself). Can you please describe in more
detail what causes this particular issue?
> > Even though it's "wrong". Maintaining a user-facing program like
> > Emacs is 70% dealing with bugs and misfeatures in other systems we're
> > interfacing with.
>
> I'm trying to figure out how all of that fits together in Wayland to
> hopefully fix it in GTK upstream. Hard-coding real modifier values is
> very fundamentally wrong under both X and GTK, and leads to extremely
> hard-to-diagnose problems down-the-road.
Instead of hard-coding them, we could have them in some Lisp data
structure, where both changing them and eliminating them altogether
will be much easier. Just an idea.
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Thomas Schneider, 2022/06/20
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Po Lu, 2022/06/20
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Stefan Kangas, 2022/06/22
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Po Lu, 2022/06/22
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Lars Ingebrigtsen, 2022/06/23
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Po Lu, 2022/06/23
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",",
Eli Zaretskii <=
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Po Lu, 2022/06/23
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Eli Zaretskii, 2022/06/23
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Po Lu, 2022/06/23
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Eli Zaretskii, 2022/06/23
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Po Lu, 2022/06/23
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Eli Zaretskii, 2022/06/23
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Kévin Le Gouguec, 2022/06/24
- bug#56117: 29.0.50; pgtk does not distinguish between <kp-separator> and "."/",", Kévin Le Gouguec, 2022/06/24