From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.devel Subject: Re: [display-buffer] a way to make it behave as before? Date: Tue, 21 Jun 2011 11:11:56 +0900 Organization: Emacsen advocacy group Message-ID: References: <4DFB7705.2000401@gmx.at> <4DFF1223.5030100@gmx.at> <4DFF3BA8.3070007@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1308622350 18395 80.91.229.12 (21 Jun 2011 02:12:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 21 Jun 2011 02:12:30 +0000 (UTC) Cc: emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 21 04:12:26 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QYqRz-0005GC-SJ for ged-emacs-devel@m.gmane.org; Tue, 21 Jun 2011 04:12:23 +0200 Original-Received: from localhost ([::1]:51689 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYqRz-0007bJ-1Z for ged-emacs-devel@m.gmane.org; Mon, 20 Jun 2011 22:12:23 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:40136) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYqRh-0007ap-9e for emacs-devel@gnu.org; Mon, 20 Jun 2011 22:12:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QYqRg-0004IE-6B for emacs-devel@gnu.org; Mon, 20 Jun 2011 22:12:05 -0400 Original-Received: from orlando.hostforweb.net ([216.246.45.90]:37744) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYqRg-0004I2-0Z for emacs-devel@gnu.org; Mon, 20 Jun 2011 22:12:04 -0400 Original-Received: from localhost ([127.0.0.1]:36624) by orlando.hostforweb.net with esmtpa (Exim 4.69) (envelope-from ) id 1QYqRe-00076q-GT; Mon, 20 Jun 2011 21:12:02 -0500 X-Face: #kKnN,xUnmKia.'[pp`; Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu; B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (cygwin) Cancel-Lock: sha1:VEJ5+YhUXTnchsNldkNsGy9nXDk= X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.hostforweb.net X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-detected-operating-system: by eggs.gnu.org: Linux 2.6? (barebone, rare!) X-Received-From: 216.246.45.90 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:140749 Archived-At: martin rudalics wrote: >> The *scratch* window appears in an Emacs frame. Say it is the >> first frame. Type `C-x 5 b RET' there. The *Messages* window >> will appear in a new Emacs frame. Say it is the second frame. >> And then type `C-x 4 f ~/.emacs RET' in the second frame. Hmm, >> the .emacs window appears in the first frame. I updated the bzr copy, rebuilt Emacs with it, launched Emacs with the -Q option, and saw the behavior unchanged. emacs -Q C-x 5 b *Messages* RET C-x 4 f ~/.emacs RET -> the file appears in the *other frame*. It might be right in a literal sense because the ~/.emacs file appears in the *other window* even if it is not in the frame in which the `C-x 4 f' command is invoked, and even if it is a major visible change of Emacs. However, there is a case that violates that specification: emacs -Q C-x 5 2 C-x 4 f ~/.emacs RET -> the file appears in the *other window* of the current frame. [...] > It shouldn't for emacs -Q. And in this regard you're right. I > remembered that someone wanted to change the default value of > `display-buffer-reuse-frames' to t and have set the default value of > `display-buffer-alist' accordingly. That's what you've seen earlier > (but not in the scenario above!). I'll take that back. Meanwhile, try > the steps below which will anticipate my change and tell me whether it > works. >>> If you want to avoid that another frame showing the buffer already is >>> used, replace in all reuse-window specifiers you find in >>> `display-buffer-alist' the last element by nil. >> >>> That is, wherever you see an object like >> >>> (reuse-window nil same visible) >> >>> replace the term `visible' by nil >> >>> (reuse-window nil same nil) >> >>> so only the selected and not all visible frames get inspected. I tried this: emacs -Q (setcdr (cddr (assq 'reuse-window (car display-buffer-alist))) (list nil)) C-x 5 b *Messages* RET C-x 4 f ~/.emacs RET The behavior unchanged, i.e., the file appears in the other frame. Well, does it happen with only Emacs built on cygwin? Ok, I'll test them in Linux in home, later. Regards,