[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#11566: 24.0.97; `read-from-minibuffer': focus to standalone minibuff

From: Eli Zaretskii
Subject: bug#11566: 24.0.97; `read-from-minibuffer': focus to standalone minibuffer frame?
Date: Tue, 29 May 2012 23:20:07 +0300

> From: "Drew Adams" <address@hidden>
> Cc: <address@hidden>, <address@hidden>
> Date: Tue, 29 May 2012 12:15:26 -0700
> When `dired-mark-pop-up' calls `dired-pop-to-buffer' (inside a
> `save-window-excursion', a new frame is created (to show the *Marked Files*). 
> The new frame gets the input focus, and its border is highlighted.  Can't tell
> about the stacking order, since my standalone minibuffer frame does not 
> overlap
> it.

This part is clear, but would it be possible for you to arrange the
windows so that the stacking order is also apparent?

> Then when `dired-mark-pop-up' calls `read-from-minibuffer' immediately
> thereafter, the input focus remains where it was, and likewise the border
> highlighting.

I understand that read-from-minibuffer pops up a minibuffer frame, or
at least it should.  Does that frame become the topmost in the
stacking order after read-from-minibuffer is called, or does it stay
below other windows, like it was before the call to


reply via email to

[Prev in Thread] Current Thread [Next in Thread]