From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stephen Berman <stephen.berman@gmx.net>, 23746@debbugs.gnu.org
Subject: bug#23746: 25.0.95; Doc fixes (grammar, typos, clarification)
Date: Sat, 11 Jun 2016 16:21:19 -0400 [thread overview]
Message-ID: <CAM-tV--zcUa2zF1-eEiA9PuoFTAn_rRMdwhkSeTPPZvmBicJ6A@mail.gmail.com> (raw)
In-Reply-To: <83bn37h6o0.fsf@gnu.org>
On Sat, Jun 11, 2016 at 3:22 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> >
>> > 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".
>
As a native English speaker, "your Lisp program may wish telling the
process" sounds obviously incorrect (though I'm not sure how to
explain why in terms of grammatical rules). Whereas, "your Lisp
program may wish to tell the process" is correct.
next prev parent reply other threads:[~2016-06-11 20:21 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
2016-06-11 20:21 ` Noam Postavsky [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV--zcUa2zF1-eEiA9PuoFTAn_rRMdwhkSeTPPZvmBicJ6A@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=23746@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.