From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Stephen Berman <stephen.berman@gmx.net>, emacs-devel@gnu.org
Subject: Re: Frame title problem
Date: Mon, 08 Nov 2010 11:45:53 +0900 [thread overview]
Message-ID: <87eiawh6se.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <4CD6C219.6070500@swipnet.se>
Jan Djärv writes:
>
>
> Stephen J. Turnbull skrev 2010-11-07 15.52:
> > > So I changed Emacs so it lets the X libs set WM_CLIENT_MACHINE.
> >
> > Given the quality of the standard, the only use I can think of is as a
> > heuristic for "readable host name" in frame decorations. If so and
> > the Xlibs will do this for you, this is the Right Thing.
> >
>
> WM_CLIENT_MACHINE is used by managers to kill off bad clients when they don't
> respond. It uses _NET_WM_PID and WM_CLIENT_MACHINE to determine if the pid is
> local.
Too bad the WM, then, because as you pointed out WM_CLIENT_MACHINE is
not defined in a way that's very useful for that purpose. As a client
property, it could be almost anything. Furthermore, it shouldn't be a
client property; really, this should be transparent to the client, set
in one of the shell widgets.
Anyway, this shouldn't matter to Emacs, Emacs never infloops, right? ;-)
next prev parent reply other threads:[~2010-11-08 2:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 14:55 Frame title problem Stephen Berman
2010-11-05 16:12 ` Julien Danjou
2010-11-05 23:07 ` Stephen Berman
2010-11-06 8:17 ` Andreas Schwab
2010-11-06 12:29 ` Stephen Berman
2010-11-06 17:05 ` Jan Djärv
2010-11-06 19:44 ` Stephen Berman
2010-11-06 20:14 ` Jan Djärv
2010-11-06 22:06 ` Stephen Berman
2010-11-07 11:28 ` Jan Djärv
2010-11-07 14:52 ` Stephen J. Turnbull
2010-11-07 15:13 ` Jan Djärv
2010-11-08 2:45 ` Stephen J. Turnbull [this message]
2010-11-08 8:55 ` Stephen Berman
2010-11-06 8:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eiawh6se.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.