From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: Killing a frame sometimes kills emacs Date: Tue, 11 Oct 2011 08:46:58 +0200 Message-ID: <87sjn03tzx.fsf@thinkpad.tsdh.de> References: <87d3flnxoo.fsf@thinkpad.tsdh.de> <83fwkhdld0.fsf@gnu.org> <871uw04lr9.fsf@thinkpad.tsdh.de> <87sjog35jj.fsf@thinkpad.tsdh.de> <4E5F7ECD.9060601@swipnet.se> <838vq8e0x5.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1318315636 6160 80.91.229.12 (11 Oct 2011 06:47:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 11 Oct 2011 06:47:16 +0000 (UTC) Cc: "Jan D." , schwab@linux-m68k.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 11 08:47:11 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RDW7K-0007uf-Pc for ged-emacs-devel@m.gmane.org; Tue, 11 Oct 2011 08:47:10 +0200 Original-Received: from localhost ([::1]:34749 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDW7K-0003vW-6w for ged-emacs-devel@m.gmane.org; Tue, 11 Oct 2011 02:47:10 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:49990) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDW7H-0003vR-0R for emacs-devel@gnu.org; Tue, 11 Oct 2011 02:47:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDW7E-0003l9-HY for emacs-devel@gnu.org; Tue, 11 Oct 2011 02:47:06 -0400 Original-Received: from deliver.uni-koblenz.de ([141.26.64.15]:45014) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDW7C-0003kG-EX; Tue, 11 Oct 2011 02:47:02 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by deliver.uni-koblenz.de (Postfix) with ESMTP id A011CD22FE; Tue, 11 Oct 2011 08:47:00 +0200 (CEST) X-Virus-Scanned: amavisd-new at uni-koblenz.de Original-Received: from deliver.uni-koblenz.de ([127.0.0.1]) by localhost (deliver.uni-koblenz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BheDDAJ5O7ZE; Tue, 11 Oct 2011 08:47:00 +0200 (CEST) X-CHKRCPT: Envelopesender noch tassilo@member.fsf.org Original-Received: from thinkpad.tsdh.de (tsdh.uni-koblenz.de [141.26.67.142]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by deliver.uni-koblenz.de (Postfix) with ESMTPSA id 00884D22FC; Tue, 11 Oct 2011 08:46:59 +0200 (CEST) In-Reply-To: <838vq8e0x5.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 01 Sep 2011 18:29:26 +0300") User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 141.26.64.15 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:144872 Archived-At: Eli Zaretskii writes: >> Date: Thu, 01 Sep 2011 14:47:09 +0200 >> From: "Jan D." >> CC: Andreas Schwab , Eli Zaretskii , >> emacs-devel@gnu.org >> >> From Emacs point of view, localhost:0 and unix:0 and :0 are three >> different displays, even if they physically are the same. > > Can't we do something in Emacs so it understood that they are on the > same display? That won't fix the GTK problem, but at least it will > work around it in this particular use case. And I think it's a Good > Thing in general, no? Any news on that front? I'm still accidentally killing emacs at least twice a day. And I'm already trying hard not to fire up an emacsclient X11 frame form external GTK apps, which is really really annoying. For example, when I click on a textfile link in a browser, I have to be sure to save it and then open it from inside emacs, instead of simply letting the browser invoke emacsclient after which I would have a frame that would kill emacs when being deleted... With resepect to the Emacs 24 release, it's very likely that a lot of users will suffer from this issue, so although it's a gtk bug, there should be some workaround (probably enabled by default). For me and I guess for most users, localhost:0, unix:0 (*), :0.0, and :0 are all the same in practice, only localhost:1 or :2 actually mean other displays. So I'd simply strip localhost and unix before the colon and dot-zeros. (Maybe there should be an option for that, or some lisp function that would be called to transform the display name if it is defined...) Bye, Tassilo (*) I'm not too sure with unix:0. I know such an entry only from xorg.conf to tell the xserver where the font server is running.