unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: Frame title problem
Date: Sat, 06 Nov 2010 13:29:00 +0100	[thread overview]
Message-ID: <87eiayeiur.fsf@escher.home> (raw)
In-Reply-To: m2eiaylvcj.fsf@igel.home

On Sat, 06 Nov 2010 09:17:16 +0100 Andreas Schwab <schwab@linux-m68k.org> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> which is just the default value of frame-title-format, i.e., there is no
>> sign of the mysterious appendage " <@escher.home> " in the xprop
>> output.  What does that mean?
>
> Look for WM_CLIENT_MACHINE, if that doesn't match hostname then kwin
> assumes the client is remote and appends the marker to the title.

Thanks, I didn't know that.

WM_CLIENT_MACHINE(STRING) = "escher.home"

When I use xprop on my Emacs 23.1.91 build or on the Emacs 23.1 built by
openSUSE, I get

WM_CLIENT_MACHINE(STRING) = "escher"

On all three Emacsen system-name is "escher.home".  $HOST and $HOSTNAME
are "escher".  In /etc/hosts "escher.home" is the
Full-Qualified-Hostname and "escher" is the Short-Hostname.  So why is
WM_CLIENT_MACHINE the former instead of the latter on Emacs 24?

Steve Berman




  reply	other threads:[~2010-11-06 12:29 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 [this message]
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
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

  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=87eiayeiur.fsf@escher.home \
    --to=stephen.berman@gmx.net \
    --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).