From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 30207@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#30207: 27.0.50; [PATCH] other-window-for-scrolling returns window on daemon frame
Date: Wed, 02 May 2018 22:44:03 +0300 [thread overview]
Message-ID: <83in85q1vg.fsf@gnu.org> (raw)
In-Reply-To: <87zi1h6g20.fsf@tcd.ie> (contovob@tcd.ie)
> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Wed, 02 May 2018 19:57:59 +0100
> Cc: Noam Postavsky <npostavs@users.sourceforge.net>
>
> +@kindex C-M-S-v
> +@findex scroll-other-window-down
> The usual scrolling commands (@pxref{Display}) apply to the selected
> -window only, but there is one command to scroll the next window.
> +window only, but there are two commands to scroll the next window.
^^^^^^^^^^^^^^^^^^^^^^
I'd just say "there are commands".
> @kbd{C-M-v} (@code{scroll-other-window}) scrolls the window that
> -@kbd{C-x o} would select. It takes arguments, positive and negative,
> -like @kbd{C-v}. (In the minibuffer, @kbd{C-M-v} scrolls the help
> -window associated with the minibuffer, if any, rather than the next
> -window in the standard cyclic order; @pxref{Minibuffer Edit}.)
> +@kbd{C-x o} would select upward.
^^^^^^^^^^^^^
This makes the sentence ambiguous: it is not clear whether "upward"
goes with "scroll" or with "select". Either say "scrolls upward" at
the beginning of the sentence, or maybe explain the "upward" part in a
separate sentence (and what does "upward" mean here anyway -- does the
text or the viewport move upward?).
Thanks.
next prev parent reply other threads:[~2018-05-02 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:57 bug#30207: 27.0.50; [PATCH] other-window-for-scrolling returns window on daemon frame Basil L. Contovounesios
2018-01-22 18:59 ` martin rudalics
2018-01-23 0:07 ` Basil L. Contovounesios
2018-01-23 0:29 ` Noam Postavsky
2018-01-23 1:06 ` Basil L. Contovounesios
2018-01-23 1:29 ` Noam Postavsky
2018-01-23 13:28 ` Basil L. Contovounesios
2018-05-02 18:57 ` Basil L. Contovounesios
2018-05-02 19:44 ` Eli Zaretskii [this message]
2018-05-03 13:03 ` Basil L. Contovounesios
2018-05-03 19:00 ` Eli Zaretskii
2018-05-03 22:44 ` Basil L. Contovounesios
2018-05-10 23:48 ` Noam Postavsky
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=83in85q1vg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30207@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=npostavs@users.sourceforge.net \
/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).