From: Juanma Barranquero <lekktu@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: master 1d4862e: Fix English grammar in some doc strings and comments
Date: Fri, 8 Nov 2019 05:24:59 +0100 [thread overview]
Message-ID: <CAAeL0SQ-oX=uqFJ4X34YfHu86-=C26cEkQdAKF9gVoyWg4MWPw@mail.gmail.com> (raw)
In-Reply-To: <9ccae76c-07a2-1739-d4b0-5c13164145d3@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
On Fri, Nov 8, 2019 at 4:36 AM Paul Eggert <eggert@cs.ucla.edu> wrote:
> In many cases this sort of change does
> improve clarity,
In some cases, perhaps. In the example you quote, yes, it does perhaps
improve clarity. But here:
> -This function only handles buffers that are visiting files.
> +This function handles only buffers that are visiting files.
there's no additional clarity. It could also be argued that, in those cases
where the result is less natural-sounding it diminishes clarity, because it
increases the cognitive load, even if slightly so.
> and it's a good habit to use the word "only" consistently
Ralph Waldo Emerson's dictum about foolish consistency being the hobgoblin
of little minds has been quoted in this list often enough. If a change
produces a less natural sentence, that should be taken into account over
any "consistency".
> but then someone else who reads the sentence will
> internally vocalize it differently and misinterpret the scope of the
> "only".
We don't see a deluge of bug reports about misunderstanding the docs
because of some (allegedly) misplaced "only".
[-- Attachment #2: Type: text/html, Size: 1652 bytes --]
next prev parent reply other threads:[~2019-11-08 4:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191104023801.20244.67873@vcs0.savannah.gnu.org>
[not found] ` <20191104023803.36ABA20A3C@vcs0.savannah.gnu.org>
2019-11-04 12:51 ` master 1d4862e: Fix English grammar in some doc strings and comments Juanma Barranquero
2019-11-04 17:21 ` Stephen Gildea
2019-11-04 20:33 ` Joost Kremers
2019-11-04 21:37 ` Juanma Barranquero
2019-11-04 21:47 ` Stephen Berman
2019-11-04 22:03 ` Juanma Barranquero
2019-11-06 3:28 ` Richard Stallman
2019-11-07 10:47 ` Juanma Barranquero
2019-11-07 19:32 ` Richard Stallman
2019-11-07 19:55 ` Lars Ingebrigtsen
2019-11-08 3:35 ` Paul Eggert
2019-11-08 4:24 ` Juanma Barranquero [this message]
2019-11-08 21:31 ` Paul Eggert
2019-11-08 21:51 ` Juanma Barranquero
2019-11-08 4:33 ` Lars Ingebrigtsen
2019-11-09 3:31 ` Richard Stallman
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='CAAeL0SQ-oX=uqFJ4X34YfHu86-=C26cEkQdAKF9gVoyWg4MWPw@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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.