all messages for Emacs-related lists mirrored at yhetil.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: "Alexander Prähauser" <alexander.praehauser@gmx.at>
Cc: 65068@debbugs.gnu.org
Subject: bug#65068: 29.1; xkb-interception interaction causes problems with key combinations
Date: Wed, 23 Aug 2023 19:39:11 +0800	[thread overview]
Message-ID: <87v8d66l9c.fsf@yahoo.com> (raw)
In-Reply-To: <87sf8a81ht.fsf@gmx.at> ("Alexander Prähauser"'s message of "Wed, 23 Aug 2023 13:02:28 +0200")

Alexander Prähauser <alexander.praehauser@gmx.at> writes:

> So, what should I do next?

Assuming that you've applied the patch, press the problematic key
sequence and reply with the subsequent printouts.

TIA.





  reply	other threads:[~2023-08-23 11:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87v8dv2ib3.fsf@gmx.at>
2023-08-09  0:02 ` bug#65068: 29.1; xkb-interception interaction causes problems with key combinations Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 13:31   ` Alexander Prähauser
2023-08-16  1:29     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-16  7:50       ` Alexander Prähauser
2023-08-16  8:02         ` Alexander Prähauser
2023-08-16 12:51         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-16 14:04           ` Alexander Prähauser
2023-08-17  1:09             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17  2:37               ` Alexander Prähauser
2023-08-17  2:45                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17  3:28                   ` Alexander Prähauser
2023-08-17  4:41                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 13:35                       ` Alexander Prähauser
2023-08-23 11:02                         ` Alexander Prähauser
2023-08-23 11:39                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-23 14:05                             ` Alexander Prähauser
2023-08-24  0:00                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 11:06                                 ` Alexander Prähauser
2023-08-24  9:56                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 14:12                                     ` Alexander Prähauser
2023-08-24 12:41                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-24 15:34                                         ` Alexander Prähauser
2023-08-25  2:49                                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-25 10:11                                             ` Alexander Prähauser
2023-08-25  8:23                                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found]                                                 ` <87o7iv34z0.FSF@yahoo.com>
2023-08-25 10:36                                                   ` Alexander Prähauser
2023-08-26  1:39                                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-26 11:39                                                       ` Alexander Prähauser
2023-08-26 10:01                                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-26 10:08                                                           ` Eli Zaretskii

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=87v8d66l9c.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=65068@debbugs.gnu.org \
    --cc=alexander.praehauser@gmx.at \
    --cc=luangruo@yahoo.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.