Re: master f0ff20be51: * src/emacs.c (main): Improve accuracy of daemon warning message on PGTK.

[Sean Whitton <spwhitton@spwhitton.name>]

Hello,

On Tue 05 Apr 2022 at 10:30pm -04, Po Lu via Mailing list for Emacs changes wrote:

> diff --git a/src/emacs.c b/src/emacs.c
> index 2a4dcc2c2c..acb409fcb7 100644
> --- a/src/emacs.c
> +++ b/src/emacs.c
> @@ -1734,12 +1734,25 @@ main (int argc, char **argv)
>  	sockfd = SD_LISTEN_FDS_START;
>  #endif /* HAVE_LIBSYSTEMD */
>
> -#ifdef USE_GTK
> +      /* On X, the bug happens because we call abort to avoid GLib
> +	 crashes upon a longjmp in our X error handler.
> +
> +         On PGTK, GTK calls exit in its own error handlers for either
> +         X or Wayland.  Display different messages depending on the
> +         window system to avoid referring users to the wrong GTK bug
> +         report.  */
> +#ifdef HAVE_PGTK
> +      fputs ("Due to a limitation in GTK 3, Emacs built with PGTK will simply exit when a"
> +	     "display connection is closed."
> +	     "\nThere is no way to fix this problem, so if you want to use Emacs on Wayland"
> +	     "on multiple displays and have Emacs survive disconnects, you lose.",

Nice idea to avoid referring users to a bug report that doesn't apply to
pgtk.  But is there truly "no way to fix this problem" in the pgtk case
too?  Is it really that fundamental to the design of GTK3?

-- 
Sean Whitton