all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Andrew Tropin <andrew@trop.in>
Cc: 56653@debbugs.gnu.org
Subject: bug#56653: 29.0.50; S-SPC is treated as SPC in pgtk
Date: Wed, 20 Jul 2022 12:12:13 +0530	[thread overview]
Message-ID: <87edyggu9m.fsf@gmail.com> (raw)
In-Reply-To: <875yjs49di.fsf@trop.in> (Andrew Tropin's message of "Wed, 20 Jul 2022 08:54:17 +0300")

[புதன் ஜூலை 20, 2022] Andrew Tropin wrote:

> 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 known issue.  From etc/PROBLEMS,

    ** Certain keys such as 'C-S-u' are not reported correctly.

    Some keys with modifiers such as Shift and Control might not be
    reported correctly due to incorrectly written GTK input method
    modules.  This is known to happen to 'C-S-u' and 'C->', which are
    misreported as 'C-u' and '>'.

    To disable the use of GTK input methods, evaluate:

      (pgtk-use-im-context nil)

    This will also cause system input methods and features such as the
    Compose key to stop working.

    On X Windows, users should not use Emacs configured with PGTK, since
    this and many other problems do not exist on the regular X builds.





  reply	other threads:[~2022-07-20  6:42 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 [this message]
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

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=87edyggu9m.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --cc=56653@debbugs.gnu.org \
    --cc=andrew@trop.in \
    /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.