[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame
From: |
Eli Zaretskii |
Subject: |
bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame |
Date: |
Tue, 05 Jul 2022 19:24:02 +0300 |
> Date: Tue, 5 Jul 2022 15:59:00 +0000
> Cc: rudalics@gmx.at, monnier@iro.umontreal.ca, 56305@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > > After typing C-x C-c, rather than exiting, this particular Emacs
> > > prompts:
>
> > > "Active processes exist; kill them and exit anyway? (yes or no) "
>
> > > on MBF and it opens a window *Process List* on NF.
>
> > Sounds right to me: the frame where Emacs presents some important
> > information has focus. If you think this is wrong, please tell why.
>
> Well, I don't have a firm opinion on this, but yes-or-no-p is an active
> function, here. We always leave the minibuffer as the selected window
> for this function, certainly when we've a normal minibuffer in the frame.
> Why should it be different when we've got a minibuffer-only frame?
>
> Also, the mechanism by which NF gets the focus in the bug scenario
> appears to be random. When the focus starts out in NF and we do C-x C-c,
> the focus moves to MBF. This is inconsistent.
>
> The place where the randomness takes effect is the
>
> Fredirect_frame_focus (gfocus, frame);
>
> in do_switch_frame I drew attention to yesterday.
Do you have a suggestion for a change there to improve the behavior?
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/02
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, martin rudalics, 2022/07/03
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/03
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Eli Zaretskii, 2022/07/03
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/04
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Eli Zaretskii, 2022/07/04
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/04
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Eli Zaretskii, 2022/07/04
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/05
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame,
Eli Zaretskii <=
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/05
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/06
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Eli Zaretskii, 2022/07/06
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/06
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Stefan Monnier, 2022/07/06
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Andreas Schwab, 2022/07/06
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/06
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Andreas Schwab, 2022/07/06
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/06
- bug#56305: 29.0.50; 'yes-or-no-p' deselects minibuffer frame, Alan Mackenzie, 2022/07/07