From: Robert Pluim <rpluim@gmail.com>
To: chad <yandros@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Sean Whitton <spwhitton@spwhitton.name>,
Yuuki Harano <masm+emacs@masm11.me>,
EMACS development team <emacs-devel@gnu.org>
Subject: Re: Question about pgtk -- is it meant to fix the disconnect crash bug?
Date: Mon, 08 Mar 2021 08:55:06 +0100 [thread overview]
Message-ID: <878s6yt6zp.fsf@gmail.com> (raw)
In-Reply-To: <CAO2hHWab=KJ0m=Ln8dt0qpTzgVBep2ShTmZbX=NjKo4Rk1bFhw@mail.gmail.com> (chad's message of "Fri, 5 Mar 2021 12:35:11 -0800")
>>>>> On Fri, 5 Mar 2021 12:35:11 -0800, chad <yandros@gmail.com> said:
chad> I can't help but notice that Wayland offers a potential "solution" by
chad> simply not supporting the underlying functionality that triggers the
chad> problem. In terms of "kicking the can down the road", the basic Wayland
chad> approach is "We're making something that you might use as a can. We do not
chad> promise that 'kicking' will apply to it, and explicitly disclaim any
chad> concept of 'road'." They're doing this to keep the problem more tractable;
chad> the emacs/gtk bug is one example of the sort of thing that they're
chad> explicitly labelling "Somebody Else's Problem".
For Wayland you can use waypipe to forward to a different display.
Robert
--
prev parent reply other threads:[~2021-03-08 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 22:51 Question about pgtk -- is it meant to fix the disconnect crash bug? Sean Whitton
2021-03-04 14:44 ` Robert Pluim
2021-03-04 15:35 ` Yuuki Harano
2021-03-04 22:10 ` chad
2021-03-04 22:57 ` Daniele Nicolodi
2021-03-05 2:06 ` chad
2021-03-05 2:27 ` Stefan Monnier
2021-03-05 6:43 ` Eli Zaretskii
2021-03-08 11:04 ` David De La Harpe Golden
2021-03-05 6:38 ` Eli Zaretskii
2021-03-05 20:35 ` chad
2021-03-08 7:55 ` Robert Pluim [this message]
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=878s6yt6zp.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=masm+emacs@masm11.me \
--cc=spwhitton@spwhitton.name \
--cc=yandros@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).