[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: Wed, 30 May 2012 21:43:07 +0300

> From: "Drew Adams" <address@hidden>
> Cc: <address@hidden>, <address@hidden>
> Date: Tue, 29 May 2012 14:31:39 -0700
> Being on top, having the input focus, and having the borders highlighted all
> seem to be independent (not necessarily coupled).

Yes, that's true.

> After you answer these questions, `*Marked Files*' is popped up and you are
> asked for the chmod value (e.g. `go+w').  It is for that last input reading 
> that
> the problem arises: the input focus is in the *Marked Files* frame.

Is the input focus there, or does the input you type arrive at that
frame (instead of the minibuffer frame)?  As we established, the frame
that has focus and the frame that gets the input can be different
frames, thanks to redirect-frame-focus.

I see in the code that read-from-minibuffer (or, rather, one of its
subroutines) does the equivalent of the following:

   (if minibuffer-auto-raise
       (raise-frame minibuffer-frame))
   (or (eq (selected-frame) minibuffer-frame)
       (redirect-frame-focus minibuffer-frame))

Does your setup have minibuffer-auto-raise set to a non-nil value?  If
not, can you see if setting it non-nil fixes the problem?  (I'm not
saying that this should be the fix, I'm just trying to figure out
which part(s) of read-from-minibuffer fail to do their job.)

reply via email to

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