From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: [evilborisnet@netscape.net: weird behavior of ediff with multiple displays] Date: Thu, 08 Dec 2005 14:27:38 -0500 Message-ID: References: <20051207235332.3E7B520734B@kiferdesk.lmc.cs.sunysb.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1134070937 32541 80.91.229.2 (8 Dec 2005 19:42:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 8 Dec 2005 19:42:17 +0000 (UTC) Cc: emacs-devel@gnu.org, evilborisnet@netscape.net Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 08 20:42:09 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EkRZ1-0005ym-O5 for ged-emacs-devel@m.gmane.org; Thu, 08 Dec 2005 20:36:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EkRZK-0001SH-6A for ged-emacs-devel@m.gmane.org; Thu, 08 Dec 2005 14:36:42 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EkRRY-0007XW-Ec for emacs-devel@gnu.org; Thu, 08 Dec 2005 14:28:40 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EkRRX-0007Wp-HV for emacs-devel@gnu.org; Thu, 08 Dec 2005 14:28:39 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EkRRW-0007Wj-BS for emacs-devel@gnu.org; Thu, 08 Dec 2005 14:28:39 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EkRSa-0004qD-NQ for emacs-devel@gnu.org; Thu, 08 Dec 2005 14:29:44 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1EkRQY-00012R-3g; Thu, 08 Dec 2005 14:27:38 -0500 Original-To: Michael Kifer In-reply-to: <20051207235332.3E7B520734B@kiferdesk.lmc.cs.sunysb.edu> (message from Michael Kifer on Wed, 07 Dec 2005 18:53:32 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:47246 Archived-At: I don't think this is the right thing to do in all cases. This shouldn't happen when there is another frame that already has a minibuffer. I don't like the idea of making one frame use another frame's minibuffer, as a default. If you want to do that, you can do it explicitly, by specifying a different value for the `minibuffer' frame parameter. But the thing Emacs does automatically is create a separate minibuffer frame. I just commented out an incorrect change which would have altered that. For some reason emacs adds the separate minibuffer frame when it works over the ssh tunnel and displays frames on the local machine (while running on a remote). Perhaps the code that creates the separate minibuffer frame needs to specify different arguments in that case. The code is in make_frame_without_minibuffer. Would someone like to suggest a patch to make it DTRT in this case?