unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Štěpán Němec" <stepnem@gmail.com>, 39778@debbugs.gnu.org
Subject: bug#39778: [PATCH] checkdoc: Don't mistake "cf." for sentence end
Date: Tue, 25 Feb 2020 08:35:00 -0800 (PST)	[thread overview]
Message-ID: <7982367d-3711-4dd3-ac78-097bfe966235@default> (raw)
In-Reply-To: <8736ayac57.fsf@gmail.com>

> > Yes.
> >
> > But even better is to remove uses of "Cf." (which
> > is not so common nowadays, and is understood by
> > fewer and fewer readers).  It can typically be
> > replaced by something as simple as "Compare" or
> > sometimes even just "See also".
> 
> Do you have any hard data for your claims?

No, and I won't bother looking for it (which doesn't
mean that such data doesn't exist).

> Couldn't the same be argued about "e.g." vs "for
> example" or "i.e." vs "that is"?

Anyone could argue that if they wanted to, of course.

I wouldn't argue it.  In my experience, those two,
and "etc.", are pretty commonly recognized and
understood ("i.e." probably less so than the others,
sometimes being misunderstood as the same as "e.g.").

> Is "cf." really so much less common?

I think it is, but I won't try to support that as a fact.

> Anyway, it is probably largely subjective, but unless you can bring up
> many examples of potential further requests (I can't think of anything
> else myself), just adding "cf." shouldn't hurt, should it?

I never said that removing the bug of 2-spaces after
"cf." would hurt or is a bad idea.

In fact, I said, "Yes."  It's a good idea.  Even
better is to remove occurrences of "cf.", but yes,
that fix should be done anyway, in case someone
does use "cf."





  reply	other threads:[~2020-02-25 16:35 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 [this message]
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
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=7982367d-3711-4dd3-ac78-097bfe966235@default \
    --to=drew.adams@oracle.com \
    --cc=39778@debbugs.gnu.org \
    --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).