From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <stefankangas@gmail.com>, 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 13:35:30 +0200 [thread overview]
Message-ID: <87ilkeu3r1.fsf@gmail.com> (raw)
In-Reply-To: <83h6zyye3f.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Oct 2022 13:38:28 +0300")
>>>>> On Thu, 20 Oct 2022 13:38:28 +0300, Eli Zaretskii <eliz@gnu.org> said:
Eli> I don't understand many of these changes. They seem to be personal
Eli> stylistic preferences, in which case please revert them: there's
Eli> nothing wrong with alternative stylistic preferences.
Most of them are preferences, but this one:
>> -on. @xref{Eglot and Buffers}, for more details of what does Eglot
>> -management of a buffer entail.
>> +on. @xref{Eglot and Buffers}, for more details of what Eglot
>> +management of a buffer entails.
The original is not wrong, it just scans somewhat awkwardly.
>> -languages which are only supported by the @code{etags} backend.
>> +languages that are only supported by the @code{etags} backend.
Eli> And this one? What's wrong with using "which" in that case?
Nothing, except that there are some grammarians who believe that there
is an iron-clad infallible rule which governs when to use 'which'
versus 'that', which most of us donʼt care about [1] (and Iʼve yet to
see an example where using the 'wrong' one was unclear).
Robert
Footnotes:
[1] Please nobody try to explain this rule. Itʼs been done, it
doesnʼt need to be done again.
--
next prev parent reply other threads:[~2022-10-20 11:35 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 [this message]
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
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=87ilkeu3r1.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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.