unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rudalics@gmx.at, Gregory Heytings <gregory@heytings.org>,
	64152@debbugs.gnu.org
Subject: bug#64152: 29.0.92; 'redirect-frame-focus' is broken
Date: Wed, 21 Jun 2023 12:22:18 +0000	[thread overview]
Message-ID: <ZJLresoBcTA9uZw4@ACM> (raw)
In-Reply-To: <83sfan74fk.fsf@gnu.org>

Hello, Eli.

On Mon, Jun 19, 2023 at 20:22:23 +0300, Eli Zaretskii wrote:
> > Date: Mon, 19 Jun 2023 14:26:22 +0000
> > From: Gregory Heytings <gregory@heytings.org>
> > cc: martin rudalics <rudalics@gmx.at>, 64152@debbugs.gnu.org


> > >> That change has immediate consequences for interactions based on 
> > >> read_minibuf.  With emacs -Q evaluate (make-frame '((minibuffer . 
> > >> nil))) and in the frame created thusly type C-x C-f.  At this time it 
> > >> is impossible to access the minibuffer-less frame using C-x o, C-x 5 o, 
> > >> the window manager's Alt-TAB or any other key combination.  All these 
> > >> key combinations used to work in the given configuration ever since. 
> > >> With a minibuffer-only frames setup, the minibuffer window has become 
> > >> "modal".

> > > This works in Emacs 28, so the minibuffer-follows-selected-frame changes 
> > > aren't the culprit.  Bisection will be appreciated.


> > The culprit is 9cd72b02b6.

> Thanks.

> Alan, could you please look into fixing this?  Perhaps the recipe
> posted by Martin explains the rationale for having that "obscure,
> obsolete code" you removed?

> This is a regression in Emacs 29, so we should try fixing it on the
> emacs-29 branch.

It's fixed on the emacs-29 branch (Martin has tested the patch).  Should
I commit it to the release branch?

-- 
Alan Mackenzie (Nuremberg, Germany).





  parent reply	other threads:[~2023-06-21 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-18 14:26 bug#64152: 29.0.92; 'redirect-frame-focus' is broken martin rudalics
2023-06-18 15:27 ` Eli Zaretskii
2023-06-19 14:26   ` Gregory Heytings
2023-06-19 17:22     ` Eli Zaretskii
2023-06-20 10:06       ` Alan Mackenzie
2023-06-20 16:48       ` Alan Mackenzie
2023-06-21  6:36         ` martin rudalics
2023-06-21 12:22       ` Alan Mackenzie [this message]
2023-06-21 12:50         ` Eli Zaretskii
2023-06-21 14:34           ` Alan Mackenzie

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=ZJLresoBcTA9uZw4@ACM \
    --to=acm@muc.de \
    --cc=64152@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gregory@heytings.org \
    --cc=rudalics@gmx.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).