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: Mon, 05 Dec 2005 23:32:34 +0200 Organization: JURTA Message-ID: <87k6ejns9c.fsf@jurta.org> References: <87wtinrypp.fsf@jurta.org> <87u0dqm5ta.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 1133818643 21471 80.91.229.2 (5 Dec 2005 21:37:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 5 Dec 2005 21:37:23 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 05 22:37:21 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EjNzn-0006J5-V9 for ged-emacs-devel@m.gmane.org; Mon, 05 Dec 2005 22:35:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EjNzx-0001IB-5X for ged-emacs-devel@m.gmane.org; Mon, 05 Dec 2005 16:35:49 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EjNzm-0001I4-IN for emacs-devel@gnu.org; Mon, 05 Dec 2005 16:35:38 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EjNzk-0001Hq-Qt for emacs-devel@gnu.org; Mon, 05 Dec 2005 16:35:38 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EjNzk-0001Hn-NW for emacs-devel@gnu.org; Mon, 05 Dec 2005 16:35:36 -0500 Original-Received: from [194.126.101.111] (helo=mail.neti.ee) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EjO0J-0000wE-Ez for emacs-devel@gnu.org; Mon, 05 Dec 2005 16:36:11 -0500 Original-Received: from mail.neti.ee (80-235-34-231-dsl.mus.estpak.ee [80.235.34.231]) by Relayhost1.neti.ee (Postfix) with ESMTP id B86A31EAE; Mon, 5 Dec 2005 23:35:38 +0200 (EET) Original-To: lorentey@elte.hu (=?utf-8?Q?K=C3=A1roly_L=C5=91rentey?=) In-Reply-To: (=?utf-8?Q?K=C3=A1roly=09L=C5=91rentey's?= message of "Mon, 05 Dec 2005 15:44:27 +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:47020 Archived-At: > Now, I like these definitions as it makes more sense for me to keep > the buffer cycle frame-local, but they do have one disadvantage: the > `next-buffer'/`prev-buffer' cycle will not usually contain all > buffers---just those that were displayed in the current frame. To > reach the rest, the user needs to use `switch-to-buffer', or > equivalent. This is a grave disadvantage. `next-buffer' and `prev-buffer' should be able to cycle all buffers. > AFAICS there have not yet been any Emacs releases with > `next-buffer'/`prev-buffer', so if the frame-local behaviour is > preferable (I think it is), then it should be safe to change them now. BTW, not having `prev-buffer' in a Emacs release also gives an opportunity to rename `prev-buffer' to `previous-buffer' to be consistent with all other similar functions where currently we have: prev-buffer previous-button previous-char-property-change previous-complete-history-element previous-completion previous-error previous-error-no-select previous-frame previous-history-element previous-line previous-matching-history-element previous-multiframe-window previous-overlay-change previous-property-change previous-single-property-change previous-window -- Juri Linkov http://www.jurta.org/emacs/