From: Eli Zaretskii <eliz@gnu.org>
To: Jonathan Marten <jjm@keelhaul.me.uk>
Cc: 25062@debbugs.gnu.org
Subject: bug#25062: 24.5; Frame title (with "%b" format) changes when going to minibuffer
Date: Tue, 29 Nov 2016 19:37:52 +0200 [thread overview]
Message-ID: <83mvgixk3z.fsf@gnu.org> (raw)
In-Reply-To: <6551952.t1DPFT6gTp@keelhaul> (message from Jonathan Marten on Tue, 29 Nov 2016 15:55:30 +0000)
> From: Jonathan Marten <jjm@keelhaul.me.uk>
> Date: Tue, 29 Nov 2016 15:55:30 +0000
>
> When using the "%b" substitution in frame-title-format (the default
> value includes this when there are multiple frames), the user would
> expect the name of the buffer that they are editing to be shown. This
> happens, but when going to the minibuffer for any sort of prompt the
> title changes to the buffer name of the minibuffer - "*Minibuf-0*" or
> similar. This may be what is happening internally, but it is an
> implementation detail which does not need to be revealed. The user
> might wonder why the window title is changing just because they are
> being prompted for some information.
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?
> 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.
Thanks.
next prev parent reply other threads:[~2016-11-29 17:37 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 [this message]
2016-11-30 9:22 ` Jonathan Marten
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mvgixk3z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25062@debbugs.gnu.org \
--cc=jjm@keelhaul.me.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.