David Reitter <[EMAIL PROTECTED]> writes: > I don't know if this is a bug or not, so I'll post it here: > > If I open a second frame, then do C-x C-f in one of them and press > tab so that the window is split and I get a *Completions* buffer in > one frame, and when I then select the second frame and do a C-x C-f > there, I don't get another *Completions* buffer there, but an error > message that appears in the first frame: > > "Command attempted to use minibuffer while in minibuffer" > > This happens with standard settings, on the GNU/Linux port as well as > on Carbon, no matter what display-buffer-reuse-frames is. > > Is that a bug? >
I don't think you could call it a bug. Maybe a carbon based error! The problem is that you are midway through a command and emacs is waiting for data to be entered in the minibuffer. When you try to execute a second C-x C-f, emacs tries to use the minibuffer again, but its already in use by the previous find-file command. I think the issue is that while emacs has multiple frames, there is really only one minibuffer - each frame doesn't have its own minibuffer. Essentially, you cannot use a command which requires the minibuffer when your half way through executing a command which is already using the minibuffer. You would probably be able to use any command in the second frame which does not require the minibuffer without problems. regards, Tim -- Tim Cross The e-mail address on this message is FALSE (obviously!). My real e-mail is to a company in Australia called rapttech and my login is tcross - if you really need to send mail, you should be able to work it out! _______________________________________________ Help-gnu-emacs mailing list Help-gnu-emacs@gnu.org http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
