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: Sat, 03 Dec 2005 19:46:57 +0200 Organization: JURTA Message-ID: <87u0dqm5ta.fsf@jurta.org> References: <87wtinrypp.fsf@jurta.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1133632423 6635 80.91.229.2 (3 Dec 2005 17:53:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 3 Dec 2005 17:53:43 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 03 18:53:41 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EibY0-0003jw-Nl for ged-emacs-devel@m.gmane.org; Sat, 03 Dec 2005 18:51:45 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EibY2-000563-PY for ged-emacs-devel@m.gmane.org; Sat, 03 Dec 2005 12:51:46 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EibXk-00055t-EL for emacs-devel@gnu.org; Sat, 03 Dec 2005 12:51:28 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EibXi-00055h-Tn for emacs-devel@gnu.org; Sat, 03 Dec 2005 12:51:28 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EibXi-00055e-R3 for emacs-devel@gnu.org; Sat, 03 Dec 2005 12:51:26 -0500 Original-Received: from [194.126.101.111] (helo=mail.neti.ee) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EibXu-0008EV-8Y for emacs-devel@gnu.org; Sat, 03 Dec 2005 12:51:38 -0500 Original-Received: from mail.neti.ee (80-235-41-212-dsl.mus.estpak.ee [80.235.41.212]) by Relayhost1.neti.ee (Postfix) with ESMTP id 24A501628; Sat, 3 Dec 2005 19:51:38 +0200 (EET) Original-To: lorentey@elte.hu (=?utf-8?Q?L=C5=91rentey_K=C3=A1roly?=) In-Reply-To: (=?utf-8?Q?L=C5=91rentey=09K=C3=A1roly's?= message of "Sat, 03 Dec 2005 18:03:36 +0100") 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:46941 Archived-At: >> The current implementation of `buffer-list' frame parameter doesn't >> preserve the correct ordering of buffers selected in the same frame. >> >> After using `next-window' in one frame, `previous-window' in another >> frame gets the buffer buried in the first frame, but not in the >> same frame where it is called. >> >> Since two commands `next-window' and `previous-window' make a ring >> from the buffer list, this ring becomes broken when used in two or >> more frames. > > I think you mean `next-buffer' and `prev-buffer' here, no? This is exactly what I meant. Sorry for being so distrait. > Does this patch fix it? Not at all. The problem is that `bury-buffer' (called from `next-buffer') removes the buffer from the frame's buffer-list. So a buried buffer is no longer available from (frame-parameter nil 'buffer-list) for `prev-buffer' called in the same frame after changing the order of buried buffers in another frame. Perhaps, there should be a separate list of buried buffers maintained in a new frame parameter. -- Juri Linkov http://www.jurta.org/emacs/