From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Buffer listing in multiple frames/ttys Date: Mon, 28 Nov 2005 09:16:04 -0800 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 1133198264 4165 80.91.229.2 (28 Nov 2005 17:17:44 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 28 Nov 2005 17:17:44 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 28 18:17:41 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EgmcE-0000N9-6d for ged-emacs-devel@m.gmane.org; Mon, 28 Nov 2005 18:16:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EgmcC-000820-UU for ged-emacs-devel@m.gmane.org; Mon, 28 Nov 2005 12:16:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Egmbs-0007xx-Kz for emacs-devel@gnu.org; Mon, 28 Nov 2005 12:16:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Egmbq-0007tX-JS for emacs-devel@gnu.org; Mon, 28 Nov 2005 12:16:12 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Egmbq-0007tP-EF for emacs-devel@gnu.org; Mon, 28 Nov 2005 12:16:10 -0500 Original-Received: from [141.146.126.228] (helo=agminet01.oracle.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1Egmbp-0003Jf-Do for emacs-devel@gnu.org; Mon, 28 Nov 2005 12:16:10 -0500 Original-Received: from rgmsgw301.us.oracle.com (rgmsgw301.us.oracle.com [138.1.186.50]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jASHV6a7005803 for ; Mon, 28 Nov 2005 11:31:07 -0600 Original-Received: from rgmsgw301.us.oracle.com (localhost [127.0.0.1]) by rgmsgw301.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jASHG4p9030422 for ; Mon, 28 Nov 2005 10:16:04 -0700 Original-Received: from dradamslap (dradams-lap.us.oracle.com [130.35.177.126]) by rgmsgw301.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id jASHG4Sm030415 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Mon, 28 Nov 2005 10:16:04 -0700 Original-To: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE 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:46707 Archived-At: > * buff-menu.el (list-buffers-noselect): Display the selected > frame's buffer list, not the global one. > > Any objections? =20 Applied. (This was my first Emacs commit, look out for breakage.) =20 The original email on this spoke only of doing this for tty, IIUC. I = don't use Emacs as tty, so I didn't object. The change seems to affect = general Emacs use, however. I was about to object now, thinking that this would show only the = buffers that had been selected in the given frame, but, trying it, I see = that it still shows all buffers in non-tty Emacs (which is good, for = me). 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. 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. 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? 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.