GNU bug report logs - #63555
emacs 29 complains that it can't connect to the display

Previous Next

Full log

Message #32 received at 63555 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: rpluim <at> gmail.com, phill <at> thesusis.net, 63555 <at> debbugs.gnu.org
Subject: Re: bug#63555: emacs 29 complains that it can't connect to the display
Date: Sat, 20 May 2023 08:51:47 +0300

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: Robert Pluim <rpluim <at> gmail.com>,  phill <at> thesusis.net,
>   63555 <at> debbugs.gnu.org
> Date: Sat, 20 May 2023 09:40:04 +0800
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > How did this work in Emacs 28, then?  IOW, which change broke this
> > feature on Wayland?
> 
> Emacs 28 didn't have a PGTK build at all.
> 
> The trick in dispnew.c doesn't work on a PGTK build, because Emacs
> doesn't know every one of the environment variables GDK backends look at
> when trying to find a default display.  So if Phillip is indeed using a
> PGTK build, there is no bug here.

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.