From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: lorentey@elte.hu (=?utf-8?Q?L=C5=91rentey_K=C3=A1roly?=) Newsgroups: gmane.emacs.devel Subject: Re: Buffer listing in multiple frames/ttys Date: Mon, 28 Nov 2005 19:24:14 +0100 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1133202465 19507 80.91.229.2 (28 Nov 2005 18:27:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 28 Nov 2005 18:27:45 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 28 19:27:39 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EgnfZ-0008LX-HN for ged-emacs-devel@m.gmane.org; Mon, 28 Nov 2005 19:24:05 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EgnfY-00035V-Ve for ged-emacs-devel@m.gmane.org; Mon, 28 Nov 2005 13:24:05 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EgnfP-00035G-46 for emacs-devel@gnu.org; Mon, 28 Nov 2005 13:23:55 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EgnfN-000354-Ip for emacs-devel@gnu.org; Mon, 28 Nov 2005 13:23:54 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EgnfN-000351-FS for emacs-devel@gnu.org; Mon, 28 Nov 2005 13:23:53 -0500 Original-Received: from [212.92.23.158] (helo=ninsei.hu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EgnfM-0008Hc-UT for emacs-devel@gnu.org; Mon, 28 Nov 2005 13:23:53 -0500 Original-Received: from walrus (walrus.inf.elte.hu [157.181.166.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by chatsubo.ninsei.hu (Postfix) with ESMTP id 419FD1AD03 for ; Mon, 28 Nov 2005 19:23:49 +0100 (CET) Original-Received: by walrus (Postfix, from userid 1000) id 2FDD9BD497; Mon, 28 Nov 2005 19:24:14 +0100 (CET) Original-To: emacs-devel@gnu.org In-Reply-To: (Drew Adams's message of "Mon, 28 Nov 2005 09:16:04 -0800") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.52 (gnu/linux) 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:46709 Archived-At: Drew Adams writes: > Function `buffer-list' (which supplies the buffer list to > list-buffers-noselect') lists all buffers - it just puts those for the > given frame first. So, this change makes the buffer-menu order be > different, depending on what frame you call it from. Yes. The list still contains all the buffers, but the buffers that were recently displayed in the current frame are listed first. > For people, like me, who use pop-up-frames =3D t, this means that the > order is usually different, depending on what _buffer_ you call it > from. That's true. Although the newly created frame is initialized with the global buffer-list, `list-buffers' populates the list using the old frame's local version. > I can live with that reordering behavior, I guess. But, it might be > best if, as before, the same order were used for the buffer menu, > regardless of which frame you call it from. I'm not sure about that > (hence, "might be") - what do others think? Well, it might be question a personal preference. I usually sort my frames thematically (one for email, one for coding, etc), so a local buffer list makes much more sense. It also seems like the only reasonable behaviour in a multi-display environment.=20=20 The iswitchb package has a similar case, and it provides the iswitchb-use-frame-buffer-list variable to let the user decide. Is the reordering really inconvenient with pop-up-frames, or is it just surprising at first? > I'm also curious how this change actually fixes the problem reported > for tty - doesn't function `buffer-list' still list all buffers, so > that all get listed in the buffer menu? I don't see where the code > does anything different for the tty case. AFAICS the submitter only wanted a local ordering; he did not want to eliminate references to buffers on other displays. --=20 K=C3=A1roly