From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tumashu@163.com, stephen.berman@gmx.net, visuweshm@gmail.com,
kupfer@rawbw.com, 58771@debbugs.gnu.org
Subject: bug#58771: 29.0.50; context submenu can not click when run emacs lucid build.
Date: Thu, 12 Jan 2023 18:34:20 +0800 [thread overview]
Message-ID: <87358gdosz.fsf@yahoo.com> (raw)
In-Reply-To: <83r0w0kwjo.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Jan 2023 10:05:15 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: Feng Shu <tumashu@163.com>, Stephen Berman <stephen.berman@gmx.net>,
>> 58771@debbugs.gnu.org, Visuwesh <visuweshm@gmail.com>
>> Date: Thu, 12 Jan 2023 11:44:17 +0800
>> From: Po Lu via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> Mike Kupfer <kupfer@rawbw.com> writes:
>>
>> > 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.
>>
>> Ah, globals.h is automatically generated by make-docfile from the
>> various *.[cm] files during the build process. This is why it is very
>> easy to end up with subtle differences in globals.h. Especially in
>> lwlib, which has no business accessing Lisp anyway.
>
> I don't think I understand the problem you are trying to fix, and the
> messages recorded by debbugs don't help (maybe some were lost or sent
> in private email?). Can you explain the relevance of globals.h to the
> subject of this bug report?
>
> Dependencies for header files are supposed to be recorded
> automatically in the deps subdirectory, as part of compilation of C
> source files, so how come something is not recompiled when its
> dependency header file changes? And I have _never_ seen any problems
> with how we generate globals.h or detect that its contents changed.
I thought only src had the AUTO_DEPENDS blurb. Seems that I'm wrong.
Mike, what are the contents of lwlib/deps/xlwmenu.d on your system?
next prev parent reply other threads:[~2023-01-12 10:34 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87358gdosz.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58771@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kupfer@rawbw.com \
--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 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.