From: Eli Zaretskii <eliz@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 28340@debbugs.gnu.org
Subject: bug#28340: 26.0.50; xterm frame titles
Date: Wed, 20 Sep 2017 10:47:26 +0300 [thread overview]
Message-ID: <83poalg6b5.fsf@gnu.org> (raw)
In-Reply-To: <20170912012122.GA11282@holos.localdomain> (message from Mark Oteiza on Mon, 11 Sep 2017 21:21:22 -0400)
> Date: Mon, 11 Sep 2017 21:21:22 -0400
> From: Mark Oteiza <mvoteiza@udel.edu>
> Cc: 28340@debbugs.gnu.org
>
> > Maybe one of the hooks provided by server.el would fit the bill?
>
> Nope, none of those appear relevant, and hooking into them does nothing
> apparent. Even doing the following, I get the title as the selected
> buffer in the previously selected frame.
>
> Messaging (frame-list) in xterm-test shows that the car of the list is
> always the new frame, but still the frame title is incorrect--a new
> frame created by emacsclient -t ends up on the scratch buffer. I say
> "ends up" because sometimes I see another buffer flash before I see the
> scratch buffer. This all seems a little buggy to me, but I know
> Bug#18137 and its ancestors were tough.
What about window-configuration-change-hook, does that help? You
could set some flag in after-make-frame-functions, and then test and
reset that flag in window-configuration-change-hook, when you see that
a buffer is switched in the frame. Would that work?
next prev parent reply other threads:[~2017-09-20 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 21:37 bug#28340: 26.0.50; xterm frame titles Mark Oteiza
2017-09-04 4:16 ` Eli Zaretskii
2017-09-12 1:21 ` Mark Oteiza
2017-09-20 7:47 ` Eli Zaretskii [this message]
2017-09-20 12:23 ` Mark Oteiza
2017-09-20 13:47 ` Eli Zaretskii
2017-09-20 16:06 ` Mark Oteiza
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=83poalg6b5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28340@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
/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).