unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Robert Pluim <rpluim@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: master f0ff20be51: * src/emacs.c (main): Improve accuracy of daemon warning message on PGTK.
Date: Wed, 06 Apr 2022 11:45:48 -0700	[thread overview]
Message-ID: <8735iqkq3n.fsf@melete.silentflame.com> (raw)
In-Reply-To: <87czhu5i9i.fsf@gmail.com>

Hello,

On Wed 06 Apr 2022 at 05:44PM +02, Robert Pluim wrote:

>>>>>> On Wed, 06 Apr 2022 08:37:20 -0700, Sean Whitton <spwhitton@spwhitton.name> said:
>     >> +#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.",
>
>     Sean> Nice idea to avoid referring users to a bug report that doesn't apply to
>     Sean> pgtk.  But is there truly "no way to fix this problem" in the pgtk case
>     Sean> too?  Is it really that fundamental to the design of GTK3?
>
> There is no way for *emacs* to fix this problem. The GTK guys have
> been sitting on it for 15 years. Iʼm sure they could fix it if they
> wanted to.

That is my understanding of the X11 bug, but the change made me think
that the status of the bug as it applies to pgtk might be subtly
different.

-- 
Sean Whitton



  reply	other threads:[~2022-04-06 18:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164921225790.11115.15669298143254852205@vcs2.savannah.gnu.org>
     [not found] ` <20220406023058.315C7C009A8@vcs2.savannah.gnu.org>
2022-04-06 15:37   ` master f0ff20be51: * src/emacs.c (main): Improve accuracy of daemon warning message on PGTK Sean Whitton
2022-04-06 15:44     ` Robert Pluim
2022-04-06 18:45       ` Sean Whitton [this message]
2022-04-06 20:12         ` Óscar Fuentes
2022-04-07  0:32           ` Po Lu
2022-04-07  0:28     ` Po Lu
2022-04-07  0:49       ` Sean Whitton
2022-04-07  1:02         ` Po Lu
2022-04-07  2:11         ` Stefan Monnier
2022-04-07  2:45           ` Po Lu
2022-04-07  3:16             ` Stefan Monnier
2022-04-07  5:32               ` Sean Whitton
2022-04-07 23:04                 ` Stefan Monnier
2022-04-08  4:09                   ` Sean Whitton
2022-04-08  5:29                     ` Sean Whitton
2022-04-08  6:13                       ` Eli Zaretskii
2022-04-08 14:06                         ` Sean Whitton

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8735iqkq3n.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).