From: Stefan Kangas <stefankangas@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
51001@debbugs.gnu.org, Tom Hughes <tom@compton.nu>
Subject: bug#51001: 28.0.50; [feature/pgtk] Wrong modifier used as meta with pgtk
Date: Wed, 1 Jan 2025 19:20:41 -0600 [thread overview]
Message-ID: <CADwFkm=D-re+YOhBTkdtpJL8wW0tf3a2G1mKMskqdqzy3BRVkQ@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmmzdcJJkC__NOyTER8b1jQvsv=UAq4m7ta99kVsZUdBvQ@mail.gmail.com> (Stefan Kangas's message of "Mon, 25 Dec 2023 10:25:00 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
> Po Lu <luangruo@yahoo.com> writes:
>
>> x-*-keysym are documented in (elisp)X11 Keysyms, so I think there is
>> nothing to be done here, save for perhaps modifying their descriptions
>> to not imply they are exclusive to X11.
>
> Could you suggest a patch for the documentation?
Friendly ping.
prev parent reply other threads:[~2025-01-02 1:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 7:51 bug#51001: 28.0.50; [feature/pgtk] Wrong modifier used as meta with pgtk Tom Hughes via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 10:25 ` Lars Ingebrigtsen
2022-09-12 16:27 ` Tom Hughes via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 2:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 16:32 ` Tom Hughes via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 8:41 ` Stefan Kangas
2023-09-03 9:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 9:46 ` Stefan Kangas
2023-12-22 14:53 ` Stefan Kangas
2023-12-24 3:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-25 18:25 ` Stefan Kangas
2025-01-02 1:20 ` Stefan Kangas [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='CADwFkm=D-re+YOhBTkdtpJL8wW0tf3a2G1mKMskqdqzy3BRVkQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=51001@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=tom@compton.nu \
/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.