[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#55684: 29.0.50; wrong-type-argument in minibuffer-only frames
From: |
Stefan Monnier |
Subject: |
bug#55684: 29.0.50; wrong-type-argument in minibuffer-only frames |
Date: |
Sat, 28 May 2022 10:22:24 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
>> @@ -1576,8 +1576,14 @@ do_switch_frame (Lisp_Object frame, int track, int
>> for_deletion, Lisp_Object nor
>> to a different window, the most recently used one, unless there is a
>> valid active minibuffer in the mini-window. */
>> if (EQ (f->selected_window, f->minibuffer_window)
>> + /* FIXME: Can this test ever fail? I.e. can 'minibuffer_window'
>> + ever contain a non-mini-buffer (and if so, should we care
>> here)? */
>> && NILP (Fminibufferp (XWINDOW (f->minibuffer_window)->contents, Qt)))
>
> Yes, the test can fail. The buffer in the mini-window might be (the
> non-active) minibuffer 0. The meaning of the argument Qt is to return
> non-nil only for active minibuffers.
Ah, indeed I missed this detail. I guess that mini window can
also hold the echo area. Thanks for the explanation,
Stefan
bug#55684: 29.0.50; wrong-type-argument in minibuffer-only frames, Alan Mackenzie, 2022/05/28
- bug#55684: 29.0.50; wrong-type-argument in minibuffer-only frames,
Stefan Monnier <=