From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 19682@debbugs.gnu.org
Subject: bug#19682: 25.0.50; `other-window' doc string should say that by default it selects win in same frame
Date: Sun, 25 Jan 2015 19:48:33 +0200 [thread overview]
Message-ID: <83ppa2rbta.fsf@gnu.org> (raw)
In-Reply-To: <c78c5328-c0eb-4b91-afa1-2dbae2d03280@default>
> Date: Sun, 25 Jan 2015 09:12:23 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 19682@debbugs.gnu.org
>
> > The doc string says:
> >
> > This function uses `next-window' for finding the window to
> > select. The argument ALL-FRAMES has the same meaning as in
> > `next-window', but the MINIBUF argument of `next-window' is
> > always effectively nil.
> >
> > This is a very clear invitation to read the documentation of
> > 'next-window', if the reader cares about which window will be
> > selected. If the reader indeed goes there, she will find there the
> > details of what you wanted her to know.
> >
> > OTOH, many uses of 'other-window' don't really care about the order
> > and the candidates, in which case that argument is of no importance
> > for them.
> >
> > So I see no reason to think this doc strings lacks something
> > important.
>
> The default interactive behavior should be described clearly,
> as the first thing in the doc string. Users, especially Lisp
> users, can read further to discover more information about
> possible argument values and behavior.
We are in violent agreement about this. It's just that I think the
current doc string does precisely that.
> But the first thing that needs to be said, very clearly, and
> preferably without any reference to arguments or other doc
> strings, is what the default behavior is.
It already does. It just doesn't divulge _all_ the details about the
selection of the "other" window.
next prev parent reply other threads:[~2015-01-25 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<733fcda9-19ad-4096-aa8a-7f0f47062ac2@default>
[not found] ` <<83y4oqrgkv.fsf@gnu.org>
2015-01-25 17:12 ` bug#19682: 25.0.50; `other-window' doc string should say that by default it selects win in same frame Drew Adams
2015-01-25 17:48 ` Eli Zaretskii [this message]
2016-04-30 16:44 ` Lars Ingebrigtsen
[not found] <<b0accd37-8912-4873-ad3c-2816b55cdaaa@default>
[not found] ` <<83iofur7aj.fsf@gnu.org>
2015-01-25 23:40 ` Drew Adams
2015-01-26 6:30 ` Eli Zaretskii
[not found] <<c78c5328-c0eb-4b91-afa1-2dbae2d03280@default>
[not found] ` <<83ppa2rbta.fsf@gnu.org>
2015-01-25 19:05 ` Drew Adams
2015-01-25 19:26 ` Eli Zaretskii
2015-01-25 3:33 Drew Adams
2015-01-25 16:05 ` Eli Zaretskii
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=83ppa2rbta.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19682@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).