From: Eli Zaretskii <eliz@gnu.org>
To: Herman <mahlamytsike@gmail.com>
Cc: 67628@debbugs.gnu.org
Subject: bug#67628: Emacs 29.1: (x-open-connection (getenv "DISPLAY")) gets "Display :0.0 does not exist" error
Date: Mon, 04 Dec 2023 22:11:43 +0200 [thread overview]
Message-ID: <83il5d683k.fsf@gnu.org> (raw)
In-Reply-To: <20231204193138.3bb398b8@Elitebook> (message from Herman on Mon, 4 Dec 2023 19:31:38 +0200)
> Date: Mon, 4 Dec 2023 19:31:38 +0200
> From: Herman <mahlamytsike@gmail.com>
>
> 'x-create-frame' succeeds, but 'x-open-connection' fails with same display argument.
>
> This error "Display :0.0 does not exist" happens only, when variable 'debug-on-error' is non-nil. When 'debug-on-error' is nil, the error is not present. I.e. it works on the principle - you get what you are looking for.
It could be that the code catches the error and proceeds, but your
setting debug-on-error non-nil prevents that.
Why do you need to set debug-on-error in that case?
next prev parent reply other threads:[~2023-12-04 20:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 17:31 bug#67628: Emacs 29.1: (x-open-connection (getenv "DISPLAY")) gets "Display :0.0 does not exist" error Herman
2023-12-04 20:11 ` Eli Zaretskii [this message]
2023-12-04 22:44 ` Herman
2023-12-05 12:30 ` Eli Zaretskii
2023-12-05 12:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-06 11:54 ` Eli Zaretskii
2023-12-06 12:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-06 12:38 ` Eli Zaretskii
2023-12-06 12:40 ` Eli Zaretskii
2023-12-06 12:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-06 13:15 ` Eli Zaretskii
2023-12-07 1:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 9:12 ` Eli Zaretskii
2023-12-06 12:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-06 13:10 ` 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=83il5d683k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67628@debbugs.gnu.org \
--cc=mahlamytsike@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.