From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: don provan Newsgroups: gmane.emacs.help Subject: Re: C-x C-f in two frames -> "user minibuffer while in Date: 04 Jul 2005 00:52:44 -0700 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1120464010 12992 80.91.229.2 (4 Jul 2005 08:00:10 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 4 Jul 2005 08:00:10 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jul 04 10:00:09 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DpLrL-0006g0-Vo for geh-help-gnu-emacs@m.gmane.org; Mon, 04 Jul 2005 09:59:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DpLoA-00024c-Ji for geh-help-gnu-emacs@m.gmane.org; Mon, 04 Jul 2005 03:56:02 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.comcast.com!news.comcast.com.POSTED!not-for-mail Original-NNTP-Posting-Date: Mon, 04 Jul 2005 02:52:31 -0500 Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 Original-Lines: 38 Original-NNTP-Posting-Host: 24.5.243.171 Original-X-Trace: sv3-JZxTFug0G0LYs+p8+02Z0JqjNFcCyWWAvgt2+7B4PzNOdQiia//UfRJOKvB2vqjxownzfGgXE0zMOTg!V7qEp7IbhWic+WWWFWNQDyTpS+ZGmTm4Jrre+F4qzb6eFUJM Original-X-Complaints-To: abuse@comcast.net X-DMCA-Complaints-To: dmca@comcast.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 Original-Xref: shelby.stanford.edu gnu.emacs.help:132310 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:27786 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:27786 Miles Bader writes: > dkcombs@panix.com (David Combs) writes: > >>If you set enable-recursive-minibuffers to t it works. > >>(setq enable-recursive-minibuffers t) > > > > That is, what *disadvantages* from setting it on? What bewares > > of having it on? > > It apparently confuses beginners greatly when they accidentally end up > with a recursive minibuffer. Apparently? You really mean to say it's never confused you? I'm impressed. Anyway, I'm sure that's the main reason. Another reason, I would guess, is that there are a few bugs. Every once in a while, I run into cases where the wrong key map is active or the mini-buffer is prompting for one thing but doing completion for another. But even so, I agree that most experienced Emacs users would probably prefer recursive minibuffers enabled, especially once they get used to it. The original question sounds like the user expected each frame to have its own, independent minibuffer. Even with minibuffers enabled, the minibuffers in each frame are tied together so that, if I understand things correctly, there's really only one recursive stack, and the current top interaction typically attached to the current frame. Also, I don't think a single command such as ^x^f can recurse on itself, as would be required in the original example. If you ^x^f and then switch to another window and do a second ^x^f, as far as I can tell, the first ^x^f is always aborted. I think the original poster expected to be able to do two file-find's at the same time, one in each minibuffer of the two frames. -don