From: Stephen Berman <stephen.berman@gmx.net>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: Frame title problem
Date: Sat, 06 Nov 2010 23:06:58 +0100 [thread overview]
Message-ID: <87y696cdj1.fsf@escher.home> (raw)
In-Reply-To: <4CD5B740.2080205@swipnet.se> ("Jan Djärv"'s message of "Sat, 06 Nov 2010 21:14:56 +0100")
On Sat, 06 Nov 2010 21:14:56 +0100 Jan Djärv <jan.h.d@swipnet.se> wrote:
> They probably just use hostname, but Emacs goes through the motions
> (i.e. gethostbyname) to get the fqdn and that ends up in system-name.
I reported this to the KDE bugtracker
(https://bugs.kde.org/show_bug.cgi?id=256258) and got this response:
> --- Comment #1 from Martin Gräßlin <kde martin-graesslin com> 2010-11-06 22:53:24 ---
> This looks like an emacs bug to me. Please see the standard for it:
> http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.2.9
>
>> The client should set the WM_CLIENT_MACHINE property (of one of the
>> TEXT types) to a string that forms the name of the machine running
>> the client as seen from the machine running the server.
>
> I assume for the server it will just be escher and not the fqdn. It is
> rather unusual to identify the local machine with a fqdn.
>
> Anyway it's not a bug in kwin, but a regression in emacs. If they
> change something like that, they should revert and not tell window
> managers to adjust their code.
Steve Berman
next prev parent reply other threads:[~2010-11-06 22:06 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 [this message]
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=87y696cdj1.fsf@escher.home \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
/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).