From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: rpluim@gmail.com, phill@thesusis.net, 63555@debbugs.gnu.org
Subject: bug#63555: emacs 29 complains that it can't connect to the display
Date: Sat, 20 May 2023 11:16:11 +0300 [thread overview]
Message-ID: <83v8gns9is.fsf@gnu.org> (raw)
In-Reply-To: <87fs7r342i.fsf@yahoo.com> (message from Po Lu on Sat, 20 May 2023 14:33:09 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: rpluim@gmail.com, phill@thesusis.net, 63555@debbugs.gnu.org
> Date: Sat, 20 May 2023 14:33:09 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Why cannot we "simulate -nw" where we issue the error message that we
> > cannot connect to the display server? At that point, we presumably
> > already know that the default display could not be found.
>
> That happens very late in the initialization process, in
> `normal-top-level'.
What function(s) is/are used at that point which tells us a GUI
session is impossible? Can we invoke those same functions earlier
during startup to realize this fact where we still can start as -nw?
next prev parent reply other threads:[~2023-05-20 8:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:51 bug#63555: emacs 29 complains that it can't connect to the display Phillip Susi
2023-05-17 14:09 ` Phillip Susi
2023-05-19 6:11 ` Eli Zaretskii
2023-05-19 7:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-19 13:26 ` Robert Pluim
2023-05-19 14:52 ` Eli Zaretskii
2023-05-19 15:44 ` Robert Pluim
2023-05-20 1:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-20 5:51 ` Eli Zaretskii
2023-05-20 6:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-20 8:16 ` Eli Zaretskii [this message]
2023-05-20 8:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-20 12:58 ` Eli Zaretskii
2023-05-21 0:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-21 5:41 ` Eli Zaretskii
2023-05-21 6:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-21 11:16 ` Eli Zaretskii
2023-05-20 1:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.63555.D63555.168458752424255.notifdone@debbugs.gnu.org>
2023-05-20 17:35 ` bug#63555: closed (Re: bug#63555: emacs 29 complains that it can't connect to the display) Phillip Susi
2023-05-22 7:29 ` Robert Pluim
2023-05-22 9:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-22 10:05 ` Robert Pluim
2023-05-22 11:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-22 11:28 ` Robert Pluim
2023-05-22 12:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-22 13:37 ` Phillip Susi
2023-05-23 0:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-23 14:59 ` Phillip Susi
2023-05-24 0:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-25 15:38 ` Phillip Susi
2023-05-26 1:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-26 8:38 ` Robert Pluim
2023-05-26 15:54 ` Phillip Susi
2023-05-27 0:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-30 17:31 ` Phillip Susi
2023-05-31 1:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-22 16:44 ` Phillip Susi
2023-05-22 17:05 ` Robert Pluim
2023-05-23 14:58 ` Phillip Susi
2023-06-08 6:02 ` Daan Ro
2024-07-14 21:00 ` bug#63555: emacs 29 complains that it can't connect to the display Peter Oliver
2024-07-20 9:00 ` Eli Zaretskii
2024-08-04 7:50 ` Eli Zaretskii
2024-08-17 8:19 ` Eli Zaretskii
2024-08-17 8:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-31 8:00 ` Eli Zaretskii
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=83v8gns9is.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63555@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=phill@thesusis.net \
--cc=rpluim@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.