From: martin rudalics <rudalics@gmx.at>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: dave@boostpro.com, Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Subwindow terminology
Date: Mon, 07 Nov 2011 11:18:15 +0100 [thread overview]
Message-ID: <4EB7B067.1060904@gmx.at> (raw)
In-Reply-To: <874nygon6g.fsf@uwakimon.sk.tsukuba.ac.jp>
> No, I'll just deal with the fallout when XEmacs needs to sync to this
> ill-conceived mess. Martin doesn't write anything about why history
> of a window tree matters to Lisp programmers,
Because Martin doesn't care.
> but instead writes many
> things like
>
> But since I apparently failed to convey the semantics of this
> variable in the Elisp manual, someone else will have to take care
> of writing such a description.
>
> and
>
> > Why do you need to talk about subwindows at all?
>
> Because I didn't give this a thought yet ;-)
>
> If he needs to repeat those statements at this point, y'all are up to
> your necks in the Big Muddy.
The term subwindow was in code and documentations for many years. If
people decide, at a certain point in time, that they don't like the term
any more, they recognize too late in what kind of Muddy they've been all
that time.
> And reading *all* of both bugs doesn't explain why history of a window
> tree matters, except to Martin personally because he's the one who has
> to make sure invariants are maintained across operations on window
> trees. But the rest of us *using* the API are counting on him to get
> those invariants right.
As stated repeatedly I never cared about the history of a window tree
and will not do so in the future.
> Any place you feel a *need* to use the term "subwindow" needs more
> thought about what you're actually doing. :-) (Of course I have an
> ulterior motive here, in that XEmacs uses the term "subwindow" for a
> completely different kind of object, a "native widget", but I think
> that sentence is nevertheless true.)
Meanwhile I removed all references to the term subwindow from code and
documentation.
martin
next prev parent reply other threads:[~2011-11-07 10:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-05 4:36 Subwindow terminology Chong Yidong
2011-11-05 11:23 ` martin rudalics
2011-11-05 12:50 ` Stephen J. Turnbull
2011-11-05 13:28 ` martin rudalics
2011-11-05 13:36 ` Stephen J. Turnbull
2011-11-05 15:05 ` martin rudalics
2011-11-05 16:54 ` Stephen J. Turnbull
2011-11-05 20:31 ` Dave Abrahams
2011-11-06 8:50 ` martin rudalics
2011-11-06 9:16 ` Dave Abrahams
2011-11-06 10:59 ` martin rudalics
2011-11-06 11:36 ` Dave Abrahams
2011-11-06 13:24 ` martin rudalics
2011-11-06 9:26 ` Stephen J. Turnbull
2011-11-06 10:59 ` martin rudalics
2011-11-06 11:11 ` Eli Zaretskii
2011-11-06 23:17 ` Stephen J. Turnbull
2011-11-07 10:18 ` martin rudalics [this message]
2011-11-08 9:55 ` Chong Yidong
2011-11-06 22:15 ` Stephen J. Turnbull
2011-11-07 10:17 ` martin rudalics
2011-11-07 10:16 ` martin rudalics
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=4EB7B067.1060904@gmx.at \
--to=rudalics@gmx.at \
--cc=dave@boostpro.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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.