From: Gregory Heytings <gregory@heytings.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Stefan Kangas <stefankangas@gmail.com>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: feature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistenciesfeature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistencies
Date: Thu, 20 Oct 2022 20:34:00 +0000 [thread overview]
Message-ID: <920c42f33fc219879daf@heytings.org> (raw)
In-Reply-To: <87a65qty8a.fsf@gmail.com>
>
> if the existing text is not clearly incorrect, don't change it, even if
> there's some guide that says it's 'wrong'. 'which' vs 'that' falls in
> that camp
>
IMHO, it doesn't. And, FWIW, here's what the CMOS says:
that; which. These are both relative pronouns. In polished American
prose, _that_ is used restrictively to narrow a category or identify a
particular item being talked about {any building that is taller must be
outside the state}; _which_ is used nonrestrictively---not to narrow a
class or identify a particular item but to add something about an item
already identified {alongside the officer trotted a toy poodle, which is
hardly a typical police dog}. _Which_ is best used restrictively only
when it is preceded by a preposition {the situation in which we find
ourselves}. Nonrestrictively, it is almost always preceded by a comma, a
parenthesis, or a dash. (In British English, writers and editors seldom
observe the distinction between the two words.) Is it a useful
distinction? Yes. The language inarguably benefits from having a
terminological as well as a punctuational means of telling a restrictive
from a nonrestrictive relative pronoun.
next prev parent reply other threads:[~2022-10-20 20:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 10:38 feature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistenciesfeature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistencies Eli Zaretskii
2022-10-20 10:59 ` Stefan Kangas
2022-10-20 13:51 ` Eli Zaretskii
2022-10-20 11:35 ` Robert Pluim
2022-10-20 12:24 ` Stefan Kangas
[not found] ` <87a65qty8a.fsf@gmail.com>
2022-10-20 13:50 ` Eli Zaretskii
2022-10-22 19:59 ` Richard Stallman
2022-10-23 5:13 ` Eli Zaretskii
2022-10-23 13:19 ` Stefan Kangas
2022-10-23 16:18 ` Eli Zaretskii
2022-10-20 15:02 ` Stefan Kangas
2022-10-20 16:18 ` Eli Zaretskii
2022-10-20 20:34 ` Gregory Heytings [this message]
2022-10-20 22:35 ` Tim Cross
2022-10-21 6:04 ` Eli Zaretskii
2022-10-21 8:41 ` Gregory Heytings
2022-10-23 19:14 ` Richard Stallman
2022-10-23 19:21 ` Eli Zaretskii
2022-10-23 19:13 ` Richard Stallman
2022-10-20 15:11 ` Rudolf Adamkovič
2022-10-20 16:20 ` 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=920c42f33fc219879daf@heytings.org \
--to=gregory@heytings.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
--cc=stefankangas@gmail.com \
/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.