From: Jonathan Marten <jjm@keelhaul.me.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25062@debbugs.gnu.org
Subject: bug#25062: 24.5; Frame title (with "%b" format) changes when going to minibuffer
Date: Wed, 30 Nov 2016 09:22:21 +0000 [thread overview]
Message-ID: <17838677.EsBG1hTTNl@keelhaul> (raw)
In-Reply-To: <83mvgixk3z.fsf@gnu.org>
On Tuesday 29 November 2016 19:37:52 Eli Zaretskii wrote:
> I actually use this feature all the time: it helps me to find the
> frame which is waiting for some input. So I don't think we should
> change that.
>
> Can't you achieve what you want by using some 'eval' form in
> frame-title-format?
Thanks for the comments; if this is intentional behaviour then everything is
working correctly. I didn't like this happening myself and so looked for a
way to customise it, and couldn't find one at the Lisp level - but then most
of my elisp experience has been with XEmacs which didn't support eval forms
within f-t-f. Following your suggestion, though, I've found a way that works
and doesn't need any Emacs changes.
> > Applying the following patch corrects this. If the selected window is a
> > minibuffer window, it evaluates the format string in the buffer of the
> > minibuffer-selected-window instead of the buffer of the minibuffer. With
> > this patch, the frame title stays the same as before when being prompted
> > in the minibuffer.
>
> Sorry, I don't think it's right to change that for everyone.
Since there is a way around it, I'll agree.
> Thanks.
--
Jonathan Marten http://www.keelhaul.me.uk
Twickenham, UK jjm@keelhaul.me.uk
next prev parent reply other threads:[~2016-11-30 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 15:55 bug#25062: 24.5; Frame title (with "%b" format) changes when going to minibuffer Jonathan Marten
2016-11-29 17:37 ` Eli Zaretskii
2016-11-30 9:22 ` Jonathan Marten [this message]
2016-11-30 14:50 ` Eli Zaretskii
[not found] <<6551952.t1DPFT6gTp@keelhaul>
[not found] ` <<83mvgixk3z.fsf@gnu.org>
2016-11-29 18:09 ` Drew Adams
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=17838677.EsBG1hTTNl@keelhaul \
--to=jjm@keelhaul.me.uk \
--cc=25062@debbugs.gnu.org \
--cc=eliz@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).