From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9875@debbugs.gnu.org
Subject: bug#9875: 24.0.90; Confusing description of the "window tree" in ELisp manual
Date: Wed, 26 Oct 2011 10:17:18 -0400 [thread overview]
Message-ID: <jwvd3dj2651.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1RJ1tK-0002EG-F9@fencepost.gnu.org> (Eli Zaretskii's message of "Wed, 26 Oct 2011 07:43:30 -0400")
> This node starts fine, by describing window-frame and window-list.
> Then it begins to describe the "window tree", and that's where things
> go wrong. The main problem is that the non-leaf nodes of the window
> tree are referred to as "windows", which makes it all too easy to
> confuse them with the leafs of the window tree, each one of which
I think the first step is to choose a single name for those, and then
use it systematically. I think we should simply call "window" the
traditional "real" "live" "leaf" windows that display a buffer. As for
the other ones, we could go for "internal window", but I think "parent
window" is better, tho maybe someone has a better idea ("compound
window", "super window", ... ?)
Stefan
next prev parent reply other threads:[~2011-10-26 14:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 11:43 bug#9875: 24.0.90; Confusing description of the "window tree" in ELisp manual Eli Zaretskii
2011-10-26 14:17 ` Stefan Monnier [this message]
2011-10-26 18:31 ` Eli Zaretskii
2011-10-26 22:21 ` Stefan Monnier
2011-10-27 7:27 ` Eli Zaretskii
2011-10-27 9:56 ` martin rudalics
2011-10-27 11:05 ` Eli Zaretskii
2011-10-27 12:36 ` Stefan Monnier
2011-10-27 12:58 ` Eli Zaretskii
2011-10-27 13:16 ` martin rudalics
2011-10-27 12:35 ` Stefan Monnier
2011-10-26 14:23 ` martin rudalics
2011-10-26 18:54 ` Eli Zaretskii
2011-10-27 9:52 ` martin rudalics
2011-10-27 11:00 ` Eli Zaretskii
2011-10-27 13:16 ` martin rudalics
2011-10-28 8:04 ` Juri Linkov
2011-10-28 9:43 ` Eli Zaretskii
2011-10-28 13:38 ` Drew Adams
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=jwvd3dj2651.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9875@debbugs.gnu.org \
--cc=eliz@gnu.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.