From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: next-error-last-buffer Date: 13 May 2004 16:28:16 +0900 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <871xluig40.fsf@mail.jurta.org> <873c6983t9.fsf@mail.jurta.org> <8765b3vm0r.fsf@mail.jurta.org> <4nn04fgeli.fsf@lifelogs.com> <87hdumto1j.fsf@mail.jurta.org> <878yfx2bv7.fsf@mail.jurta.org> <87fza4x53v.fsf@mail.jurta.org> Reply-To: Miles Bader NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084434895 16164 80.91.224.253 (13 May 2004 07:54:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 13 May 2004 07:54:55 +0000 (UTC) Cc: tzz@lifelogs.com, rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu May 13 09:54:43 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BOB3C-0000Xm-00 for ; Thu, 13 May 2004 09:54:42 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BOB3C-0005pT-00 for ; Thu, 13 May 2004 09:54:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BOAoC-0000hl-HZ for emacs-devel@quimby.gnus.org; Thu, 13 May 2004 03:39:12 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BOAm9-0000LZ-Tj for emacs-devel@gnu.org; Thu, 13 May 2004 03:37:06 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BOAlX-0000EI-6n for emacs-devel@gnu.org; Thu, 13 May 2004 03:37:03 -0400 Original-Received: from [202.32.8.214] (helo=TYO201.gate.nec.co.jp) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BOAdm-0007yi-OQ; Thu, 13 May 2004 03:28:27 -0400 Original-Received: from mailgate3.nec.co.jp (mailgate53.nec.co.jp [10.7.69.160] (may be forged)) by TYO201.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id i4D7SKp19364; Thu, 13 May 2004 16:28:20 +0900 (JST) Original-Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id i4D7SJc24708; Thu, 13 May 2004 16:28:19 +0900 (JST) Original-Received: from edtmg02.lsi.nec.co.jp ([10.26.16.202]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id i4D7SI604441; Thu, 13 May 2004 16:28:18 +0900 (JST) Original-Received: from mcsss2.ucom.lsi.nec.co.jp (localhost [127.0.0.1]) by edtmg02.lsi.nec.co.jp (8.12.10/8.12.10) with ESMTP id i4D7SH6D011467; Thu, 13 May 2004 16:28:17 +0900 (JST) Original-Received: from mctpc71 (mctpc71.ucom.lsi.nec.co.jp [10.30.118.121]) by mcsss2.ucom.lsi.nec.co.jp (8.12.10/8.12.8/EDcg v2.01-mc/1046780839) with ESMTP id i4D7SGaQ016455; Thu, 13 May 2004 16:28:16 +0900 (JST) Original-Received: by mctpc71 (Postfix, from userid 31295) id 9BB94131FC; Thu, 13 May 2004 16:28:16 +0900 (JST) Original-To: Juri Linkov System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: <87fza4x53v.fsf@mail.jurta.org> Original-Lines: 23 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23307 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23307 Juri Linkov writes: > But there is the variable `display-buffer-reuse-frames' for users who > like to reuse windows on another frames. That is too general: it affects _all_ use of display-buffer, including, crucially, `pop-to-buffer'. In that context, the effect is not just annoying, it's downright dangerous (as the user expects the keyboard focus to be the new popped-to buffer -- and it _looks_ like it is because the window is raised -- but in fact, the frame focus doesn't change). So setting `display-buffer-reuse-frames' to t is not reasonable. > I even have no objections to changing its default value to t, since I > can change it to nil in .emacs. But there is no way to ignore the > frame argument of `display-buffer' if it's specified explicitly. If it really drives you nuts, make a special variable for this case or something. But please don't change the existing behavior. -Miles -- I'd rather be consing.