From: Mike Kupfer <kupfer@rawbw.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Feng Shu <tumashu@163.com>,
Stephen Berman <stephen.berman@gmx.net>,
58771@debbugs.gnu.org, Visuwesh <visuweshm@gmail.com>
Subject: bug#58771: 29.0.50; context submenu can not click when run emacs lucid build.
Date: Wed, 11 Jan 2023 18:16:51 -0800 [thread overview]
Message-ID: <173034.1673489811@alto> (raw)
In-Reply-To: Your message of "Thu, 12 Jan 2023 09:22:35 +0800." <87o7r4eeck.fsf@yahoo.com>
Po Lu wrote:
> So what I'd like to do is to remove the reference to
> `lucid__menu_grab_keyboard' in the first place, and replace it with a
> define. Any objections?
Would this also involve removing f_lucid__menu_grab_keyboard from the
emacs_globals struct and removing the corresponding DEFVAR_BOOL in
keyboard.c? pop_up_menu() is the only place lucid__menu_grab_keyboard
is used.
mike
next prev parent reply other threads:[~2023-01-12 2:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 5:28 bug#58771: 29.0.50; context submenu can not click when run emacs lucid build Feng Shu
2022-10-25 7:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 8:35 ` Feng Shu
2022-10-25 10:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 13:58 ` Stephen Berman
2022-10-26 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 8:00 ` Stephen Berman
2022-10-26 8:18 ` Visuwesh
2022-10-26 9:40 ` Stephen Berman
2023-01-11 6:57 ` Mike Kupfer
2023-01-11 9:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-11 20:44 ` Mike Kupfer
2023-01-12 1:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12 2:16 ` Mike Kupfer [this message]
2023-01-12 3:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12 8:05 ` Eli Zaretskii
2023-01-12 10:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-13 2:43 ` Mike Kupfer
2023-01-13 7:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-13 7:32 ` Eli Zaretskii
2023-01-14 2:28 ` Paul Eggert
2023-01-14 7:25 ` Eli Zaretskii
2023-01-14 7:48 ` Paul Eggert
2023-01-13 7:35 ` Jean Louis
2023-01-12 8:56 ` Eli Zaretskii
2023-01-13 5:23 ` Mike Kupfer
2022-10-26 8:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 9:40 ` Stephen Berman
2022-10-26 9:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 2:14 ` Feng Shu
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=173034.1673489811@alto \
--to=kupfer@rawbw.com \
--cc=58771@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=stephen.berman@gmx.net \
--cc=tumashu@163.com \
--cc=visuweshm@gmail.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).