From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Spencer Bronson <spencerbronson@mac.com>
Cc: 71351@debbugs.gnu.org
Subject: bug#71351: 30.0.50; PGTK build breaks some default keybindings
Date: Tue, 04 Jun 2024 09:49:02 +0800 [thread overview]
Message-ID: <87bk4hiik1.fsf@yahoo.com> (raw)
In-Reply-To: <87ed9du3kf.fsf@mac.com> (Spencer Bronson's message of "Mon, 03 Jun 2024 14:19:44 -0700")
tags 71351 + notabug
close 71351
thanks
Spencer Bronson <spencerbronson@mac.com> writes:
> Emacs describes some keys differently when built --with-pgtk, breaking
> some default keybindings.
>
> When built with default configuration:
> 1. emacs -Q
> 2. C-h k
> 3. (I press the key that produces keycode 159)
> Result: "<XF86Forward> runs the command next-buffer" etc.
>
> When built "--with-pgtk":
> 1. emacs -Q
> 2. C-h k
> 3. (I press the key that produces keycode 159)
> Result: "<Forward> is undefined"
>
> I don't know how many keys this affects; media keys like
> "<AudioNext>"/"<XF86AudioNext>" and function keys like
> "<ScreenSaver>"/"<XF86ScreenSaver>" are affected as well, breaking
> customizations that rely on naming those keys with kbd.
The names of such keys are provided by GDK, just as they previously were
by your X library distributor, and there is little in our power as to
correcting inconsistencies between the two beyond creating additional
bindings for existing instances of the X names in Emacs.
prev parent reply other threads:[~2024-06-04 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 21:19 bug#71351: 30.0.50; PGTK build breaks some default keybindings Spencer Bronson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04 1:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=87bk4hiik1.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=71351@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=spencerbronson@mac.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 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.