From: Juri Linkov <juri@jurta.org>
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: Fri, 28 Oct 2011 11:04:35 +0300 [thread overview]
Message-ID: <87y5w55zfw.fsf@mail.jurta.org> (raw)
In-Reply-To: <E1RJNhV-0003id-S8@fencepost.gnu.org> (Eli Zaretskii's message of "Thu, 27 Oct 2011 07:00:45 -0400")
> It is unnatural to talk about "size" or "side" of a window that
> doesn't really exist on the screen!
FWIW, I have no problem imagining a window that doesn't really exist
on the screen. I imagine it as an "abstract window" with invisible
outlines that group visible windows. So I have no problem understanding
"internal windows" when reading the documentation.
It seems the source of your complaints is the duality of window
representation: data and view. When manipulating the window tree
(e.g. when saving/restoring the window tree) it makes sense to think
in terms of data - window tree with nodes. But when manipulating
windows of the screen (e.g. when splitting windows), it makes sense
to think in terms of visual representation where "internal windows"
are distinct objects (albeit invisible).
So thinking about "internal windows" requires imagination skills.
But diagrams in the Info manual help greatly.
The only problem with these diagrams is that ASCII art
doesn't distinguish between internal and live windows:
______________________________________
| ______ ____________________________ |
|| || __________________________ ||
|| ||| ___________ ___________ |||
|| |||| || ||||
|| |||| || ||||
|| ||||_____W6____||_____W7____||||
|| |||____________W4____________|||
|| || __________________________ ||
|| ||| |||
|| |||____________W5____________|||
||__W2__||_____________W3_____________ |
|__________________W1__________________|
It would help to draw live and internal windows with different lines, e.g.
______________________________________
|******** ____________________________ |
|* *| __________________________ ||
|* *||**************************|||
|* *||* ** *|||
|* *||* ** *|||
|* *||******W6***********W7*****|||
|* *||____________W4____________|||
|* *|****************************||
|* *|* *||
|* *|*************W5*************||
|***W2***|_____________W3_____________ |
|__________________W1__________________|
but this is ugly and I can't find a better way to draw them.
next prev parent reply other threads:[~2011-10-28 8:04 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
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 [this message]
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
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=87y5w55zfw.fsf@mail.jurta.org \
--to=juri@jurta.org \
--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 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).