unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: chad <yandros@gmail.com>
Cc: masm+emacs@masm11.me, emacs-devel@gnu.org, spwhitton@spwhitton.name
Subject: Re: Question about pgtk -- is it meant to fix the disconnect crash bug?
Date: Fri, 05 Mar 2021 08:38:16 +0200	[thread overview]
Message-ID: <83im66yujr.fsf@gnu.org> (raw)
In-Reply-To: <CAO2hHWZCJiMrfqRV1SSKjQVMC=sKBxWsTaW4-RB4HS=YQPr+Tw@mail.gmail.com> (message from chad on Thu, 4 Mar 2021 14:10:39 -0800)

> From: chad <yandros@gmail.com>
> Date: Thu, 4 Mar 2021 14:10:39 -0800
> Cc: Yuuki Harano <masm+emacs@masm11.me>,
>  EMACS development team <emacs-devel@gnu.org>
> 
>  I had thought that one of
>  the benefits of the pgtk branch was that it would not have this bug,
>  which plagues the old Emacs GTK builds.  Am I just making that up?
> 
> Adding a bit of historical perspective: it might be more accurate to say "the GTK people are unwilling to
> address the issue when it's caused by what some people call 'unclean gtk use' inside emacs", with the
> concomitant hope that they will more more receptive to a pure-gtk issue.

Isn't the pgtk branch supposed to produce a "clean GTK use" inside
Emacs?  I thought that was its purpose.



  parent reply	other threads:[~2021-03-05  6:38 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 [this message]
2021-03-05 20:35     ` chad
2021-03-08  7:55       ` Robert Pluim

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=83im66yujr.fsf@gnu.org \
    --to=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).