Re: Question about minibuffer and child frames (Posframe)

[Gerd Möllmann]

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

>> Must find out something else firwt though. With master pulled today
>> C-x o errors with "no next window". But of course not with -q and not
>> right from the beginning but caused by something unknown 👀.
>
> FWIW workaround: Use windmove with windmove-allow-all-windows set to t
> :-/. Hope someone fixes that soon.

I think I found it: it's transient-posframe.

When transient-posframe falls back to using a window instead of a frame
because Posframe is not workable, it uses an existing Emacs window, the
selected window:

  (defun transient-posframe--show-buffer (buffer _alist)
    "Show BUFFER in posframe and we do not use _ALIST at this period."
    (when (posframe-workable-p)
      (let* ((posframe
              (posframe-show buffer ...
        (frame-selected-window posframe))))
--------^

Transient puts a `no-other-window' window property on the window it is
using, and that property is not removed, and stays on that window after
the Transient is done.

So don't use transient-posframe-mode on terminals unless your Emacs
has child frames on ttys. Which is probably the reason I've not noticed
beforem because I'n using my tty-child-franes for a while now.

Yanghao Xie, the author of transient-posframe, is in CC. Maybe he's
interested because it can take a while until tty child frames land.