From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: quarl+dated+1093194046.34955e@nospam.quarl.org, emacs-devel@gnu.org
Subject: Re: window-list
Date: Wed, 18 Aug 2004 13:03:40 -0500 (CDT) [thread overview]
Message-ID: <200408181803.i7II3eo23397@raven.dms.auburn.edu> (raw)
In-Reply-To: <m34qn0d91s.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
Kim Storm wrote:
I don't recall any discussion about the need for that change, but
I guess there was a reason....
To make the function do what both its docstring and the documentation
in the Elisp manual claim it does:
-- Function: window-list &optional frame minibuf window
This function returns a list of the windows on FRAME, starting
with WINDOW. If FRAME is `nil' or omitted, the selected frame is
used instead; if WINDOW is `nil' or omitted, the selected window
is used instead.
So I do not believe that there _has_ been a change in documented
behavior. The documentation was changed quite a while ago, for
"compatibility with XEmacs". (Revision 1.322 to window.c on Nov 19,
2000, by Gerd.) I guess the change must have been discussed back
then. The new behavior was never correctly implemented, until
Richard's change.
As I already pointed out, unless I am misunderstanding, one can get
the behavior Karl wants, from Elisp, using:
(window-list frame minibuf (frame-first-window frame))
Sincerely,
Luc.
next prev parent reply other threads:[~2004-08-18 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 17:25 window-list Karl Chen
2004-08-18 10:39 ` window-list Kim F. Storm
2004-08-18 18:03 ` Luc Teirlinck [this message]
2004-08-19 9:50 ` window-list Kim F. Storm
2004-08-20 4:49 ` window-list Richard Stallman
2004-08-20 21:04 ` window-list Karl Chen
2004-08-21 16:50 ` window-list Richard Stallman
2004-08-21 17:00 ` window-list Luc Teirlinck
2004-08-18 17:41 ` window-list Luc Teirlinck
2004-08-18 20:18 ` window-list Karl Chen
2004-08-18 18:47 ` window-list 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=200408181803.i7II3eo23397@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=quarl+dated+1093194046.34955e@nospam.quarl.org \
/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.