unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.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: Sun, 03 Sep 2023 17:06:23 +0800	[thread overview]
Message-ID: <87msy3lj74.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkm=2=kTwCCGQ4DG3kUosUkjzcUOx_FU6UcNP+kZJ7uUssg@mail.gmail.com> (Stefan Kangas's message of "Sun, 3 Sep 2023 01:41:32 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

> Is it worth documenting this trick somewhere?  Po Lu, what do you
> think?

Don't we already document the x-*-keysym variables somewhere?  I'll
check later today.





  reply	other threads:[~2023-09-03  9:06 UTC|newest]

Thread overview: 11+ 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 [this message]
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

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=87msy3lj74.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=51001@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.com \
    --cc=stefankangas@gmail.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 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).