From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org, 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: Wed, 26 Feb 2020 07:03:39 -0800 (PST) [thread overview]
Message-ID: <2f8f9280-5171-45ab-b935-e90149a88954@default> (raw)
In-Reply-To: <E1j6mtV-0000Ce-Hp@fencepost.gnu.org>
>> "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.
Really? Was that the question? I didn't
understand that that question was being raised.
Why shouldn't Emacs support editing files that
use _any_ text? Was there an argument against
letting one edit such files? Or did you perhaps
mean something special (what?) here by "support"?
The bug reported was only about Emacs treating
the `.' as a sentence end. I think everyone
agreed that that's a bug to be fixed ("cf."
does not end a sentence, generally).
Beyond the bug, the thread discussed the use
of "cf." by Emacs's own doc. Yes, that was a
change of subject from the bug report. But
that was the only real discussion (question)
here, I think. Unless I missed someone's
argument in favor of two spaces after "cf.".
next prev parent reply other threads:[~2020-02-26 15:03 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
2020-02-26 15:03 ` Drew Adams [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2f8f9280-5171-45ab-b935-e90149a88954@default \
--to=drew.adams@oracle.com \
--cc=39778@debbugs.gnu.org \
--cc=bzg@gnu.org \
--cc=rms@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).