From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, 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 11:05:00 -0800 (PST) [thread overview]
Message-ID: <b0accd37-8912-4873-ad3c-2816b55cdaaa@default> (raw)
In-Reply-To: <<83ppa2rbta.fsf@gnu.org>>
> > 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.
No, it does not say what the default behavior is. It does not
tell you that, by default, it switches to another window in
the same frame.
That's all that is missing. If you don't want to say that,
so be it.
I am not asking for a description of "_all_ the details about the
selection of the "other" window."
I am asking that you say what the other window is by default.
Just the information that it is in the same frame is sufficient
here. Beyond that, referring to `next-window' for details
(including, e.g., which window in the same frame) is fine.
next parent reply other threads:[~2015-01-25 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<c78c5328-c0eb-4b91-afa1-2dbae2d03280@default>
[not found] ` <<83ppa2rbta.fsf@gnu.org>
2015-01-25 19:05 ` Drew Adams [this message]
2015-01-25 19:26 ` bug#19682: 25.0.50; `other-window' doc string should say that by default it selects win in same frame Eli Zaretskii
[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] <<733fcda9-19ad-4096-aa8a-7f0f47062ac2@default>
[not found] ` <<83y4oqrgkv.fsf@gnu.org>
2015-01-25 17:12 ` Drew Adams
2015-01-25 17:48 ` Eli Zaretskii
2016-04-30 16:44 ` Lars Ingebrigtsen
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=b0accd37-8912-4873-ad3c-2816b55cdaaa@default \
--to=drew.adams@oracle.com \
--cc=19682@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).