From: Ken Raeburn <raeburn@raeburn.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs Dev <emacs-devel@gnu.org>
Subject: Re: Killing a frame sometimes kills emacs
Date: Thu, 1 Sep 2011 15:30:38 -0400 [thread overview]
Message-ID: <C4A24A47-FBC1-4089-AE61-38470984543F@raeburn.org> (raw)
In-Reply-To: <838vq8e0x5.fsf@gnu.org>
On Sep 1, 2011, at 11:29, Eli Zaretskii wrote:
>> Date: Thu, 01 Sep 2011 14:47:09 +0200
>> From: "Jan D." <jan.h.d@swipnet.se>
>> CC: Andreas Schwab <schwab@linux-m68k.org>, Eli Zaretskii <eliz@gnu.org>,
>> 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?
>
If that's the intent of the X code... I've actually seen cases where the hostname "unix" gets looked up, so maybe the rule is "unix means the local host if you don't have a machine named unix". I'm not sure if that was X11 software or something else trying to interpret $DISPLAY, though; I was looking at DNS packet traces.
In this case, ":0.0" vs ":0" is even more straightforward. According to the X man page I just looked up, at least, the default screen number is zero if omitted (not some changeable per-display default screen number), so counting those two as the same should be easy.
Ken
next prev parent reply other threads:[~2011-09-01 19:30 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 [this message]
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
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=C4A24A47-FBC1-4089-AE61-38470984543F@raeburn.org \
--to=raeburn@raeburn.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).