From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 54382-done@debbugs.gnu.org,
Torsten Bronger <bronger@physik.rwth-aachen.de>
Subject: bug#54382: 28.0.92; --with-x-toolkit=no leads to "FALLTHROUGH undefined" in Activate.c
Date: Tue, 15 Mar 2022 10:05:49 +0800 [thread overview]
Message-ID: <87v8wgrmv6.fsf@yahoo.com> (raw)
In-Reply-To: <1275e7ef-4a7c-75e4-24f6-22ad18a086be@cs.ucla.edu> (Paul Eggert's message of "Mon, 14 Mar 2022 18:54:17 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> That file had been included into oldXMenu for quite some time, it's
> just that it was included more indirectly (via config.h). So this
> isn't really a new include.
Ah okay, I'm happy then. Thanks for explaining.
> Is the idea to minimize the differences between oldXMenu and some
> ancient version of the X library? If so, that ship sailed a long time
> ago, as we've already installed several trivial porting changes like
> this.
No, not really. If the file has always been included, then I see no
harm in adding it now.
next prev parent reply other threads:[~2022-03-15 2:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 9:28 bug#54382: 28.0.92; --with-x-toolkit=no leads to "FALLTHROUGH undefined" in Activate.c Torsten Bronger
2022-03-14 9:52 ` Lars Ingebrigtsen
2022-03-14 20:17 ` Paul Eggert
2022-03-15 0:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-15 1:54 ` Paul Eggert
2022-03-15 2:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-03-14 13:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-14 13:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-14 14:45 ` Torsten Bronger
2022-03-15 0:30 ` Po Lu 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8wgrmv6.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54382-done@debbugs.gnu.org \
--cc=bronger@physik.rwth-aachen.de \
--cc=eggert@cs.ucla.edu \
--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.