all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: 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 08:02:12 -0700	[thread overview]
Message-ID: <CADwFkmmZNX66qQ1xC9RNVDU+pDPD_O9Y7Z-EVh3OX3bVEENLdQ@mail.gmail.com> (raw)
In-Reply-To: <87a65qty8a.fsf@gmail.com>

Robert Pluim <rpluim@gmail.com> writes:

> You donʼt want progressive, you want conservative:

No, I just had no idea that this particular rule was contentious:

1. I first learned about the difference between "which" or "that" on
   this list (or bug-gnu-emacs), and no one protested against the advice
   given to me at the time.

2. Any reference I could find recommended it (admittedly, I only checked
   the top 1-2 hits on the web).

> if the existing text is not clearly incorrect, donʼt change it, even
> if thereʼs some guide that says itʼs 'wrong'.

You could be a bit more generous here, perhaps.

From the advice given to me, and the sources I found, I drew the
conclusion precisely that using "that" is "clearly incorrect".  I did
not have any reason to think this advice was wrong, or stylistic
preference, or personal, or conservative, or anything of the kind.

I'm sure there are hundreds or even thousands of these pitfalls in the
English language.  When people try to improve the documentation, I think
we can point out such pitfalls.



  parent reply	other threads:[~2022-10-20 15:02 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 [this message]
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=CADwFkmmZNX66qQ1xC9RNVDU+pDPD_O9Y7Z-EVh3OX3bVEENLdQ@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@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.