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

Previous Next

Full log

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

From: Po Lu <luangruo <at> yahoo.com>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Phillip Susi <phill <at> thesusis.net>,
 63555 <at> debbugs.gnu.org
Subject: Re: bug#63555: closed (Re: bug#63555: emacs 29 complains that it
 can't connect to the display)
Date: Mon, 22 May 2023 19:15:40 +0800

Robert Pluim <rpluim <at> gmail.com> writes:

>>>>>> On Mon, 22 May 2023 17:26:27 +0800, Po Lu <luangruo <at> yahoo.com> said:
>
>     Po> The problem with this approach is that gtk_init_check initializes the
>     Po> window system upon success, so once pgtk_term_init is called in
>     Po> pgtkterm.c, the window system is set up a second time, leaving two
>     Po> display connections open...
>
> Is there anything stopping us from removing that call to gtk_init?

Yes, since the PGTK build is supposed to support multiple displays.

BTW, the other problem with calling `gtk_init_check' is that when it
returns FALSE, calling any other GTK function results in undefined
behavior.  Thus, if `gtk_init_check' is used at startup, opening a
display later becomes unsafe, even if a display connection is then
available.

Previous Next

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