unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>
Cc: 55412@debbugs.gnu.org, tanzer@swing.co.at
Subject: bug#55412: 28.1; In Emacs 28.1, using ':eval' in 'frame-title-format' doesn't work properly
Date: Wed, 18 May 2022 09:19:48 +0200	[thread overview]
Message-ID: <87d23565-b8ba-3b08-0d10-068be3b0c5fd@gmx.at> (raw)
In-Reply-To: <YoK5mjJC+7MJK2CO@ACM>

 > With the Fselect_window call in place:
 > (i) When minibuffer-follows-selected-frame is nil, and the minibuffer is
 >    the current window before switching frames with C-x 5 o, it remains the
 >    current window on returning to the first frame.
 > (ii) When minibuffer-follows-selected-frame is t (the default) and other
 >    circumstances are as in (i), the minibuffer is no longer the selected
 >    window on returning to the first frame.
 > I wanted to fix this inconsistency, I think.
 >
 > Clearly, this inconsistency is less important than frame-title-format not
 > working.

When I type M-:, save the expression to evaluate from some other frame,
and the subsequent yank inserts that expression into a normal buffer
instead of the minibuffer, the resulting behavior does not constitute a
less important inconsistency but an annoying regression.  This is one of
the things that used to work "ever since".

 > May I suggest that one of us applies your patch immediately to
 > the release branch.  I will then attempt to find a less harmful way of
 > fixing that inconsistency, and will take direction from you which branch
 > it should be committed to.

In that case please default 'minibuffer-follows-selected-frame' to nil
and then try to find a suitable solution.  Or try the patch I posted.

martin





  parent reply	other threads:[~2022-05-18  7:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 15:45 bug#55412: 28.1; In Emacs 28.1, using ':eval' in 'frame-title-format' doesn't work properly Christian Tanzer
2022-05-14 16:58 ` Eli Zaretskii
2022-05-14 17:07   ` Eli Zaretskii
2022-05-15  9:48   ` Alan Mackenzie
2022-05-15 10:16     ` Eli Zaretskii
2022-05-16 20:52   ` Alan Mackenzie
2022-05-17 13:25     ` Eli Zaretskii
2022-05-18  7:19     ` martin rudalics [this message]
2022-05-18 11:35       ` Eli Zaretskii
2022-05-18 15:01         ` martin rudalics
2022-05-18 15:12           ` Alan Mackenzie
2022-05-18 15:49           ` Alan Mackenzie
2022-05-18 16:03             ` Eli Zaretskii
2022-05-18 16:38               ` Alan Mackenzie
2022-05-18 16:51                 ` Eli Zaretskii
2022-05-20  8:23                   ` martin rudalics
2022-05-20 10:58                     ` Eli Zaretskii
2022-05-21  8:32                       ` martin rudalics
2022-05-21  8:35                         ` Eli Zaretskii
2022-05-20 11:33                     ` Alan Mackenzie
2022-05-20 12:10                       ` Eli Zaretskii
2022-05-21  8:32                       ` martin rudalics
2022-05-21  8:59                         ` Eli Zaretskii
2022-05-19  7:18             ` martin rudalics
2022-05-20 20:39   ` Alan Mackenzie
2022-05-21 11:25     ` tanzer--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-21 12:35       ` Eli Zaretskii
2022-05-22 17:34       ` Alan Mackenzie
2022-05-15  9:28 ` martin rudalics

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=87d23565-b8ba-3b08-0d10-068be3b0c5fd@gmx.at \
    --to=rudalics@gmx.at \
    --cc=55412@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=tanzer@swing.co.at \
    /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).