From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dkcombs@panix.com (David Combs) Newsgroups: gmane.emacs.help Subject: Re: C-x C-f in two frames -> "user minibuffer while in Date: Sun, 3 Jul 2005 21:47:19 +0000 (UTC) Organization: Public Access Networks Corp. Message-ID: References: NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1120427365 12623 80.91.229.2 (3 Jul 2005 21:49:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 3 Jul 2005 21:49:25 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Jul 03 23:49:20 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DpCKp-0008KP-ER for geh-help-gnu-emacs@m.gmane.org; Sun, 03 Jul 2005 23:49:07 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DpCM0-000639-C4 for geh-help-gnu-emacs@m.gmane.org; Sun, 03 Jul 2005 17:50:20 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!bloom-beacon.mit.edu!panix!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 40 Original-NNTP-Posting-Host: panix2.panix.com Original-X-Trace: reader2.panix.com 1120427239 21461 166.84.1.2 (3 Jul 2005 21:47:19 GMT) Original-X-Complaints-To: abuse@panix.com Original-NNTP-Posting-Date: Sun, 3 Jul 2005 21:47:19 +0000 (UTC) X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Original-Xref: shelby.stanford.edu gnu.emacs.help:132304 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:27779 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:27779 In article , Toto wrote: >In article , Peter Dyballa writes: >> Am 08.06.2005 um 15:18 schrieb David Reitter: >> >>> 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" >>> >> >> No, that's definitely no bug! There is in the first frame minibuffer >> waiting for your input. And since there is only one such thing, yet, >> you can't use it for something different somewhere else. >> >> I think too it would be a nice enhancement if every frame would have >> its own minibuffer. I remember that from time to time I had to use more >> than one Emacs running to get things together for an input to >> minibuffer (could have sorted this out in scratch buffer -- but then I >> would have needed to remember how I made minibuffer awaiting my input >> ...) > >If you set enable-recursive-minibuffers to t it works. >(setq enable-recursive-minibuffers t) > >So that's definitely no bug, indeed. > Sounds good -- but if it were good, why isn't "on" the default? That is, what *disadvantages* from setting it on? What bewares of having it on? Thanks, David