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: da_vid@orange.fr, Paul Eggert <eggert@cs.ucla.edu>,
70568@debbugs.gnu.org
Subject: bug#70568: 30.0.50; build warnings on 'x86_64-pc-linux-gnu'
Date: Sun, 28 Apr 2024 13:31:47 +0800 [thread overview]
Message-ID: <8734r6f3y4.fsf@yahoo.com> (raw)
In-Reply-To: <86cyqaulfj.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 28 Apr 2024 08:05:04 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 27 Apr 2024 15:20:36 -0700
>> Cc: 70568@debbugs.gnu.org
>> From: Paul Eggert <eggert@cs.ucla.edu>
>>
>> On 2024-04-27 02:37, Eli Zaretskii wrote:
>> > Paul, are those real warnings, or just false alarms?
>> Hard to say; someone who understands that part of the code would have to
>> look at it in more detail.
>
> Thanks. Perhaps Po Lu (CC'ed) can?
Definitely a false alarm, if the eassume above wasn't explicit enough.
It's impossible for a display connection not managed by Emacs to enter
functions that call x_display_info_for_display.
next prev parent reply other threads:[~2024-04-28 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 15:11 bug#70568: 30.0.50; build warnings on 'x86_64-pc-linux-gnu' David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-27 9:37 ` Eli Zaretskii
2024-04-27 22:20 ` Paul Eggert
2024-04-28 5:04 ` Eli Zaretskii
2024-04-28 5:05 ` Eli Zaretskii
2024-04-28 5:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-01 7:18 ` David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-01 7:26 ` Paul Eggert
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=8734r6f3y4.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=70568@debbugs.gnu.org \
--cc=da_vid@orange.fr \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.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).