From: Andrew Tropin <andrew@trop.in>
To: Po Lu <luangruo@yahoo.com>, Visuwesh <visuweshm@gmail.com>
Cc: 56653@debbugs.gnu.org
Subject: bug#56653: 29.0.50; S-SPC is treated as SPC in pgtk
Date: Fri, 22 Jul 2022 15:15:52 +0300 [thread overview]
Message-ID: <87lesll4w7.fsf@trop.in> (raw)
In-Reply-To: <87v8rs9gwf.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On 2022-07-20 19:12, Po Lu wrote:
> forcemerge 56653 53320
> thanks
>
> Andrew Tropin <andrew@trop.in> writes:
>
>> Everything below is additionally checked with emacs -Q.
>>
>> `C-h k M-S-SPC` show M-SPC (translated from M-S-SPC) runs the command
>> just-one-space. (works as expected).
>>
>> `C-h k S-SPC` shows SPC runs the command self-insert-command, but I
>> expected to see (traslated from S-SPC).
>>
>> In non-pgtk emacs28 it works as expected (says translated from S-SPC).
>
> This is a duplicate of bug#53200 and countless others. The Shift key
> will not be reported correctly in keyboard events until input method
> developers fix their thing, or you turn the input method off (how to do
> so is documented in etc/PROBLEMS), so reporting bugs to Emacs will not
> solve anything in particular.
>
> (It is also wholely unrelated to the issue with Super key support on
> non-GNOME compositors.)
Thank you very much for responses, sorry for duplicate report! :)
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2022-07-22 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 5:54 bug#56653: 29.0.50; S-SPC is treated as SPC in pgtk Andrew Tropin
2022-07-20 6:42 ` Visuwesh
2022-07-20 11:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-22 12:15 ` Andrew Tropin [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
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=87lesll4w7.fsf@trop.in \
--to=andrew@trop.in \
--cc=56653@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=visuweshm@gmail.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 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).