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: Fri, 22 Apr 2022 08:51:34 +0800 [thread overview]
Message-ID: <87y1zy9bzd.fsf@yahoo.com> (raw)
In-Reply-To: <87y1zy34ge.fsf@onenetbeyond.org> (dal-blazej@onenetbeyond.org's message of "Thu, 21 Apr 2022 16:18:25 +0200")
dal-blazej@onenetbeyond.org writes:
>> I guess what you have to do is to step through each statement until you
>> find out why it isn't reaching this piece of handle_one_xevent:
>
> It seems the key is ... initialized to 0 ?
>
> (gdb) p xkey
> $13 = {type = 0, serial = 0, send_event = 1466608144,
> display = 0x898f22a9e227e100, window = 140737488343872, root = 93824994679155,
> subwindow = 0, time = 93824993826130, x = 2, y = 0, x_root = 0, y_root = 0,
> state = 0, keycode = 0, same_screen = 0}
I think your Emacs is out of date, since this shouldn't be possible if
the breakpoint was set to the location I asked.
> [...]
>
> (gdb) u
> x_emacs_to_x_modifiers (dpyinfo=0x555557727a00, state=0) at xterm.c:9546
>
> (gdb) p tem
> $21 = (Lisp_Object) 0x0
>
> [...]
>
> (gdb) n
> handle_one_xevent (dpyinfo=0x555557727a00, event=0x7fffffffd5e0,
> finish=0x555555beabb8 <current_finish>, hold_quit=0x7fffffffd850)
> at xterm.c:13926
I think your copy of Emacs is very out of date. Please rebuild and try
again.
next prev parent reply other threads:[~2022-04-22 0:51 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
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 [this message]
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=87y1zy9bzd.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).