emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Frame title problem


From: Jan Djärv
Subject: Re: Frame title problem
Date: Sat, 06 Nov 2010 18:05:22 +0100
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; sv-SE; rv:1.9.2.11) Gecko/20101004 Thunderbird/3.1.5

The 23 branch does not set WM_CLIENT_MACHINE, but trunk does set it to system-name. See bug 5828 (_NET_WM_PID is useless without WM_CLIENT_MACHINE).

KWin should be able to figure out that escher and escher.home is the same machine, IMHO.

        Jan D.


Stephen Berman skrev 2010-11-06 13.29:
On Sat, 06 Nov 2010 09:17:16 +0100 Andreas Schwab<address@hidden>  wrote:

Stephen Berman<address@hidden>  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 via email to

[Prev in Thread] Current Thread [Next in Thread]