From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: dal-blazej@onenetbeyond.org
Cc: 54656@debbugs.gnu.org
Subject: bug#54656: 29.0.50; [menu] key is not read anymore
Date: Mon, 04 Apr 2022 08:18:44 +0800 [thread overview]
Message-ID: <87bkxh7laz.fsf@yahoo.com> (raw)
In-Reply-To: <87czhxu33d.fsf@onenetbeyond.org> (dal-blazej@onenetbeyond.org's message of "Mon, 04 Apr 2022 02:03:34 +0200")
dal-blazej@onenetbeyond.org writes:
> Sorry I lack comprehension of the gdb and C.
>
> If I place a breakpoint on :
>
>> static void
>> x_display_set_last_user_time (struct x_display_info *dpyinfo, Time time)
>> {
>> ...
>
> It is called to many time while initiating Emacs and I cannot verify the
> keypress. How do I do that the right way ?
Ah, sorry. Place the breakpoint here instead, inside the function
`handle_one_xevent':
case KeyPress:
==> x_display_set_last_user_time (dpyinfo, event->xkey.time);
ignore_next_mouse_click_timeout = 0;
coding = Qlatin_1;
Thanks.
next prev parent reply other threads:[~2022-04-04 0:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 19:41 bug#54656: 29.0.50; [menu] key is not read anymore dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 1:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-01 21:34 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 1:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 15:51 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-03 0:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-04 0:03 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-04 0:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-04-04 9:31 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-04 11:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-21 14:18 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-22 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-22 13:57 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-23 0:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-24 19:25 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-25 2:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-02 23:39 ` dal-blazej--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87bkxh7laz.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54656@debbugs.gnu.org \
--cc=dal-blazej@onenetbeyond.org \
--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 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).