From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Buffer listing in multiple frames/ttys Date: Wed, 07 Dec 2005 23:29:31 +0200 Organization: JURTA Message-ID: <87r78ooe3s.fsf@jurta.org> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1133992148 30938 80.91.229.2 (7 Dec 2005 21:49:08 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 7 Dec 2005 21:49:08 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 07 22:49:08 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Ek77A-0007YH-2K for ged-emacs-devel@m.gmane.org; Wed, 07 Dec 2005 22:46:16 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ek77P-0005k4-MN for ged-emacs-devel@m.gmane.org; Wed, 07 Dec 2005 16:46:31 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ek76e-0005X6-4T for emacs-devel@gnu.org; Wed, 07 Dec 2005 16:45:44 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ek76d-0005WX-Je for emacs-devel@gnu.org; Wed, 07 Dec 2005 16:45:43 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ek76d-0005WS-GS for emacs-devel@gnu.org; Wed, 07 Dec 2005 16:45:43 -0500 Original-Received: from [194.126.101.111] (helo=mail.neti.ee) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Ek77X-0005QA-Vy for emacs-devel@gnu.org; Wed, 07 Dec 2005 16:46:40 -0500 Original-Received: from mail.neti.ee (80-235-37-157-dsl.mus.estpak.ee [80.235.37.157]) by Relayhost1.neti.ee (Postfix) with ESMTP id 3F0B620E1; Wed, 7 Dec 2005 23:45:43 +0200 (EET) Original-To: "Drew Adams" In-Reply-To: (Drew Adams's message of "Wed, 7 Dec 2005 08:54:46 -0800") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Virus-Scanned: by amavisd-new-2.2.1 (20041222) (Debian) at neti.ee 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:47161 Archived-At: > I'd repeat, though, that it would make sense for the default value of the > option to come from the value of pop-up-frames: > > I still believe that most people who use pop-up-frames = t will > want to set this option to nil (so, they would prefer that that > behavior be the default for non-nil pop-up-frames), but I don't > mind setting the option to get the old behavior. > > That way, people who use one-buffer-per-frame-by-default would not need to > change anything, beyond setting pop-up-frames = t. I think that covers most > (but not all) people who set pop-up-frames = t. I still don't understand the need for a new option for one-buffer-per-frame configuration. When a new frame is created due to pop-up-frames=t, its frame-local buffer-list contains exactly one buffer which is the current buffer. So (buffer-list) is an exact equivalent of (buffer-list t). -- Juri Linkov http://www.jurta.org/emacs/