all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: bzg@gnu.org, 39778@debbugs.gnu.org, stepnem@gmail.com
Subject: bug#39778: [PATCH] checkdoc: Don't mistake "cf." for sentence end
Date: Tue, 25 Feb 2020 21:57:53 -0500	[thread overview]
Message-ID: <E1j6mtV-0000Ce-Hp@fencepost.gnu.org> (raw)
In-Reply-To: <878skqz8k2.fsf@stefankangas.se> (message from Stefan Kangas on Tue, 25 Feb 2020 22:00:29 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

      > "It is often tempting to use abbreviations such as 'no.', 'i.e.',
      > 'e.g.' 'c.f.' and 'w.r.t.'  These save little space on the page,
      > but slow readers down.

That is good advice, but it changes the subject.
The question is not whether to use those old abbreviations.
It is whether Emacs should support editing of files that do use them.

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  parent reply	other threads:[~2020-02-26  2:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 12:22 bug#39778: [PATCH] checkdoc: Don't mistake "cf." for sentence end Štěpán Němec
2020-02-25 15:49 ` Drew Adams
2020-02-25 16:02   ` Štěpán Němec
2020-02-25 16:35     ` Drew Adams
2020-02-25 16:41       ` Bastien
2020-02-25 21:00         ` Stefan Kangas
2020-02-25 21:41           ` Drew Adams
2020-02-26  2:57           ` Richard Stallman [this message]
2020-02-26 15:03             ` Drew Adams
2020-03-10  2:41               ` Richard Stallman
2020-03-10 13:58                 ` Stefan Kangas
2020-02-28 13:19 ` 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=E1j6mtV-0000Ce-Hp@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=39778@debbugs.gnu.org \
    --cc=bzg@gnu.org \
    --cc=stefan@marxist.se \
    --cc=stepnem@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.