From: Daan Ro <daanturo@gmail.com>
To: 49211@debbugs.gnu.org
Subject: bug#49211: 28.0.50; Unable to type S-SPC on feature/pgtk
Date: Sun, 25 Dec 2022 15:59:27 +0700 [thread overview]
Message-ID: <CAGNN0nCW2U06D0uzDTgbu=5DT5amDwN_7k4Ujvz7KbefVYT++g@mail.gmail.com> (raw)
In-Reply-To: <20210704.020923.309981347579909548.masm@luna.pink.masm11.me>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Hello,
I think there was a mistake when merging those bugs.
Namely
49211 : 28.0.50; Unable to type S-SPC on feature/pgtk
51002 : 28.0.50; [feature/pgtk] Some keypad keys handled as normal keys
with pgtk
53200 : 29.0.50; C-S-u shortcut fails with 'PGTK' enable
55362 : 29.0.50; Super key no longer works on Wayland
<- the different one
55660 : 29.0.50; PGTK degrades to terminal-compatible keyboard events
56653 : 29.0.50; S-SPC is treated as SPC in pgtk
49211, 51002, 53200, 55660, 56653 are caused by GTK input methods, with
imperfect workaround (give up on using GTK input methods) on the Elisp
level.
While 55362 is caused by GTK3, without user-level workarounds except by
patching
Emacs. Apparently the fix for GTK3 was landed, but reverted before the
latest
release: see https://gitlab.gnome.org/GNOME/gtk/-/issues/4913#note_1625320.
I think we should unmerge 55660 from the rest of the remaining bugs to
prevent
future confusions such as
https://yhetil.org/emacs/87lemxaahb.fsf@yahoo.com/T/#m372014fd3135e963b00bfc1439ffc0078633ad82
--
Daanturo.
[-- Attachment #2: Type: text/html, Size: 1395 bytes --]
prev parent reply other threads:[~2022-12-25 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 11:23 bug#49211: 28.0.50; Unable to type S-SPC on feature/pgtk daanturo
2021-07-02 12:20 ` Yuuki Harano
2021-07-03 9:13 ` daanturo
2021-07-03 17:09 ` Yuuki Harano
2022-12-25 8:59 ` Daan Ro [this message]
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='CAGNN0nCW2U06D0uzDTgbu=5DT5amDwN_7k4Ujvz7KbefVYT++g@mail.gmail.com' \
--to=daanturo@gmail.com \
--cc=49211@debbugs.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 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.