From: Chong Yidong <cyd@stupidchicken.com>
To: James Cloos <cloos@jhcloos.com>
Cc: Ulrich Mueller <ulm@gentoo.org>,
emacs-devel@gnu.org, schwab@linux-m68k.org,
Stefan Monnier <monnier@iro.umontreal.ca>,
Tassilo Horn <tassilo@member.fsf.org>,
"Jan D." <jan.h.d@swipnet.se>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Killing a frame sometimes kills emacs
Date: Tue, 11 Oct 2011 22:04:00 -0400 [thread overview]
Message-ID: <87vcrvm0dr.fsf@stupidchicken.com> (raw)
In-Reply-To: <m3y5wr5sz1.fsf@jhcloos.com> (James Cloos's message of "Tue, 11 Oct 2011 13:38:02 -0400")
James Cloos <cloos@jhcloos.com> writes:
> It seems, then, that emacs needs to canonicalize the DISPLAY strings
> before comparing them.
>
> I thought that I remembered some some code in libX11 and/or xtrans
> which does that, but a quick grep(1) did not illuminate any.
I'm not sure that can be made to work reliably.
Perhaps what we should do, instead, is to avoid deleting terminals in
delete_frame if Emacs is compiled with GTK. The original intention was
for Emacs to close remote X connections when we're done with them. But
if GTK responds to an X connection closing by crashing, maybe we should
just not close those X connections at all.
Tassilo, could you experiment with commenting out the terminal deletion
code in frame.c:1362, and see what the behavior is like?
next prev parent reply other threads:[~2011-10-12 2:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 20:16 Killing a frame sometimes kills emacs Tassilo Horn
2011-08-31 20:51 ` joakim
2011-08-31 23:06 ` chad
2011-09-01 2:53 ` Eli Zaretskii
2011-09-01 7:04 ` Tassilo Horn
2011-09-01 10:09 ` Tassilo Horn
2011-09-01 10:27 ` Eli Zaretskii
2011-09-01 10:42 ` Tassilo Horn
2011-09-01 10:56 ` Eli Zaretskii
2011-09-01 11:09 ` Tassilo Horn
2011-09-01 10:33 ` Andreas Schwab
2011-09-01 10:45 ` Tassilo Horn
2011-09-01 12:47 ` Jan D.
2011-09-01 13:05 ` Tassilo Horn
2011-09-01 15:29 ` Eli Zaretskii
2011-09-01 19:30 ` Ken Raeburn
2011-09-02 15:02 ` Andreas Schwab
2011-10-11 6:46 ` Tassilo Horn
2011-10-11 12:53 ` Stefan Monnier
2011-10-11 14:53 ` Tassilo Horn
2011-10-11 17:38 ` James Cloos
2011-10-11 19:17 ` Tassilo Horn
2011-10-11 19:49 ` Tassilo Horn
2011-10-12 2:04 ` Chong Yidong [this message]
2011-10-12 6:49 ` Tassilo Horn
2011-10-12 12:57 ` Stefan Monnier
2011-11-17 10:10 ` Tassilo Horn
2011-11-17 11:18 ` Chong Yidong
2011-11-17 13:45 ` Tassilo Horn
2011-11-17 16:34 ` Paul Eggert
2011-11-17 16:58 ` Tassilo Horn
2011-11-18 2:41 ` Chong Yidong
2011-11-18 2:05 ` Stefan Monnier
2011-11-18 9:38 ` Tassilo Horn
2012-01-20 23:29 ` andres.ramirez
2012-01-21 0:34 ` Glenn Morris
2012-01-21 8:02 ` andres.ramirez
2012-01-20 23:29 ` andres.ramirez
2011-10-11 17:56 ` Jan Djärv
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=87vcrvm0dr.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=cloos@jhcloos.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
--cc=tassilo@member.fsf.org \
--cc=ulm@gentoo.org \
/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).