From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 35063-done@debbugs.gnu.org
Subject: bug#35063: 26.1; Doc of window parameter `other-window'...
Date: Sat, 06 Apr 2019 11:09:13 +0300 [thread overview]
Message-ID: <83wok7a72u.fsf@gnu.org> (raw)
In-Reply-To: <a64d0fc2-03d5-44d9-b70a-cb9da1ae75c7@default> (message from Drew Adams on Sun, 31 Mar 2019 15:37:18 -0700 (PDT))
> Date: Sun, 31 Mar 2019 15:37:18 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> (elisp) `Window Parameters' should be the place where the window
> parameters are each described.
>
> A reader should not just fall upon a cop-out description such as this:
>
> `other-window'
> This parameter affects the execution of `other-window' (see Cylic
> Window Ordering)
There's nothing wrong, per se, with having the detailed description of
the parameter in a more appropriate place. It isn't a "cop-out".
> But the real bug is that when you go to node Cyclic Window Ordering you
> find nothing at all describing parameter `other-window', whose doc sent
> you there for a real description.
I added the description of other-window parameter there.
> Also, the first sentence of node `Window Parameters' says:
>
> This section describes how window parameters can be used to
> associate additional information with windows.
>
> But it doesn't seem to be mostly about that. Only the description of
> function `set-window-parameter' tells you "how window parameters can be
> used to associate additional information with windows".
I modified that sentence to not imply the actual description of the
parameters must be in this section.
> What's more, the node doesn't really tell you _why_ you would
> associate... What's that for? When would you do that? Not clear from
> this node, AFAICT. OK, a few of the parameter descriptions,
> e.g. `window-preserved-size' give an idea of what they might be used
> for. But most do not, do they?
If you read the detailed descriptions of the parameters in the context
of the functions they affect, I think this question answers itself.
Thanks.
prev parent reply other threads:[~2019-04-06 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 22:37 bug#35063: 26.1; Doc of window parameter `other-window' Drew Adams
2019-04-06 8:09 ` Eli Zaretskii [this message]
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=83wok7a72u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35063-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).