From: Matt Swift <swift@alum.mit.edu>
Subject: documentation of `buffer-list' misleading
Date: Sat, 20 Jul 2002 02:04:43 -0400 [thread overview]
Message-ID: <E17VnMB-0001ff-00@fencepost.gnu.org> (raw)
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.
Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.
In GNU Emacs 21.2.1 (i386-msvc-nt5.0.2195)
of 2002-03-19 on buffy
configured using `configure --with-msvc (12.00)'
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: ENU
locale-coding-system: iso-latin-1
default-enable-multibyte-characters: t
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
The documentation of `buffer-list' in the docstring and the elisp manual v2.7
suggests that the following form in an interactive Lisp session
should always evaluate to t, but in fact it is usually not t:
(equal
(frame-parameter nil 'buffer-list)
(buffer-list (selected-frame)))
=> nil
To make the apparent paradox clearer, one could write the equivalent form:
(equal
(frame-parameter (selected-frame) 'buffer-list)
(buffer-list (selected-frame)))
=> nil
Looking at the source in buffer.c, I see that `(buffer-list my-frame)' is
returning a list of *all* buffers (that is, the same ones as `(buffer-list
nil)' returns) in the order that `other-buffer' is going to examine them when
my-frame is the selected frame.
Having the name of the function `buffer-list' seem associated with
`other-buffer' and not with the related but different frame parameter would be
ideal, in my opinion, but I realize that changing the names now would probably
cause more problems than it resolves. Clearer documentation would suffice.
Recent input:
C-n C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p C-p
C-p C-p C-p C-p C-p C-p C-h i M-< t M-s b u f f e r
- l i s t <return> <tab> C-a C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n
C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-n C-p M-x
r e p o r t - e m a c s - b u g <return>
Recent messages:
Searching subfile elisp-19...
Searching subfile elisp-20...
Searching subfile elisp-21...
Searching subfile elisp-22...
Searching subfile elisp-23...
Searching subfile elisp-24...
Searching subfile elisp-25...
Searching subfile elisp-26...
Loading emacsbug...done
next reply other threads:[~2002-07-20 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 6:04 Matt Swift [this message]
2002-07-21 20:15 ` documentation of `buffer-list' misleading Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E17VnMB-0001ff-00@fencepost.gnu.org \
--to=swift@alum.mit.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.