unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 23746@debbugs.gnu.org
Subject: bug#23746: 25.0.95; Doc fixes (grammar, typos, clarification)
Date: Sat, 11 Jun 2016 22:22:39 +0300	[thread overview]
Message-ID: <83bn37h6o0.fsf@gnu.org> (raw)
In-Reply-To: <87d1nnofd2.fsf@gmx.net> (message from Stephen Berman on Sat, 11 Jun 2016 18:32:57 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 23746@debbugs.gnu.org
> Date: Sat, 11 Jun 2016 18:32:57 +0200
> 
> >>  If the process's buffer is displayed in a window, your Lisp program
> >> -may wish telling the process the dimensions of that window, so that
>         ^^^^^^^^^^^^
> >> -the process could adapt its output to those dimensions, much as it
>                 ^^^^^
> >> -adapts to the screen dimensions.  The following functions allow to
>                                                               ^^^^^^^^
> >> -communicate this kind of information to processes; however, not all
>     ^^^^^^^^^^^
> >> -systems support the underlying functionality, so it is best to provide
> >> -fallbacks, e.g., via command-line arguments or environment variables.
> >> +may wish to tell the process the dimensions of that window, so that
>         ^^^^^^^^^^^^
> >> +the process can adapt its output to those dimensions, much as it
>                 ^^^
> >> +adapts to the screen dimensions.  The following functions allow your
>                                                               ^^^^^^^^^^
> >> +program to communicate this kind of information to processes; however,
>     ^^^^^^^^^^^^^^^^^^^^^^
> >> +not all systems support the underlying functionality, so it is best to
> >> +provide fallbacks, e.g., via command-line arguments or environment
> >> +variables.
> >
> > This goes against the rest of the changes, which correctly made the
> > opposite replacement.  I see no reason to make the opposite change
> > here.
> 
> I don't understand what you mean; the changes in that hunk are strictly
> grammatical corrections (underlined).

Yes.  They are just backwards: "may wish telling" => "may wish to tell".





  reply	other threads:[~2016-06-11 19:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-11 15:54 bug#23746: 25.0.95; Doc fixes (grammar, typos, clarification) Stephen Berman
2016-06-11 16:08 ` Eli Zaretskii
2016-06-11 16:32   ` Stephen Berman
2016-06-11 19:22     ` Eli Zaretskii [this message]
2016-06-11 20:21       ` Noam Postavsky
2016-06-12 17:58         ` Stephen Berman
2016-06-12 18:55           ` Eli Zaretskii
2016-06-12 19:40             ` Ken Brown
2016-06-12 21:09               ` Noam Postavsky
2016-06-13  4:04                 ` Eli Zaretskii
2016-06-13  9:20                   ` Stephen Berman
2016-06-13  9:25                     ` Stephen Berman
2016-06-13 14:14                     ` Eli Zaretskii
2016-06-13 14:27                       ` Stephen Berman
2016-06-13 15:01                         ` Eli Zaretskii
2016-06-13 16:12                           ` Stephen Berman
2016-06-13 16:22                             ` Stephen Berman
2016-06-14  2:43                   ` Noam Postavsky
2016-06-14 14:29                     ` 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=83bn37h6o0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23746@debbugs.gnu.org \
    --cc=stephen.berman@gmx.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).