unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
Subject: Re: (elisp's) buffer.texi:  Vagueness in chapter "The Buffer List"
Date: Mon, 15 Aug 2005 09:47:50 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1050815093435.358A-100000@acm.acm> (raw)
In-Reply-To: <Pine.LNX.3.96.1050814094125.348A-100000@acm.acm>

Hi, Emacs!

I've sorted out my difficulties with the buffer list.  I'd like to
suggest the following patch to the Elisp manual, which I think clears up
the vagueness I was complaining about yesterday.

2005-08-15  Alan Mackenzie  <acm@muc.de>

	* buffers.texi (The Buffer List): Clarify the manipulation of the
	buffer list.


*** buffers.texi	Sun Aug 14 09:23:39 2005
--- buffers-1.43.new.texi	Mon Aug 15 09:27:29 2005
***************
*** 757,772 ****
  @section The Buffer List
  @cindex buffer list
  
!   The @dfn{buffer list} is a list of all live buffers.  Creating a
! buffer adds it to this list, and killing a buffer removes it.  The
! order of the buffers in the list is based primarily on how recently
! each buffer has been displayed in the selected window.  Buffers move
! to the front of the list when they are selected (selecting a window
! that already displays the buffer counts as selecting the buffer), and
! to the end when they are buried (see @code{bury-buffer}, below).
! Several functions, notably @code{other-buffer}, use this ordering.  A
! buffer list displayed for the user also follows this order.
  
    In addition to the fundamental Emacs buffer list, each frame has its
  own version of the buffer list, in which the buffers that have been
  selected in that frame come first, starting with the buffers most
--- 757,775 ----
  @section The Buffer List
  @cindex buffer list
  
!   The @dfn{buffer list} is a list of all live buffers.  The order of
! the buffers in the list is based primarily on how recently each buffer
! has been displayed in a window.  Several functions, notably
! @code{other-buffer}, use this ordering.  A buffer list displayed for
! the user also follows this order.
  
+   Creating a buffer adds it to the end of the buffer list, and killing
+ a buffer removes it.  Buffers move to the front of the list when they
+ are selected for display in a window (@pxref{Displaying Buffers}), and
+ to the end when they are buried (see @code{bury-buffer}, below).
+ There are no functions available to the Lisp programmer which directly
+ manipulate the buffer list.
+   
    In addition to the fundamental Emacs buffer list, each frame has its
  own version of the buffer list, in which the buffers that have been
  selected in that frame come first, starting with the buffers most


-- 
Alan Mackenzie (Munich, Germany)

      reply	other threads:[~2005-08-15  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 10:22 (elisp's) buffer.texi: Vagueness in chapter "The Buffer List" Alan Mackenzie
2005-08-15  9:47 ` Alan Mackenzie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.3.96.1050815093435.358A-100000@acm.acm \
    --to=acm@muc.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).