unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Paul Eggert <eggert@cs.ucla.edu>,
	Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: RE: [Emacs-diffs] emacs-25 26b56dc: Fix some single quotes in documentation
Date: Tue, 15 Mar 2016 17:52:52 -0700 (PDT)	[thread overview]
Message-ID: <124b0893-9ed5-4532-8ade-619609973117@default> (raw)
In-Reply-To: <56E8A49C.6050704@cs.ucla.edu>

> >>> There is plenty of precedent for straight quoting in other text
> >>> files in Emacs, as well as in etc/NEWS itself before today's
> >>> changes
> >
> > Is that because you changed `this' into curly quotes
> 
> No, I first changed etc/NEWS to use straight quotes, and switched to
> curved quotes only after what I understood to be John's suggestion to
> that effect. However, later discussion indicated that straight quotes
> were more popular, so I switched back.

Were identical straight quotes (') used in NEWS before you used
them?  I don't think so.  Except maybe for the occasional typo.

> Although grave quotes are popular Emacs source code they have
> never been the only style for all text,

In Emacs they have been.  Counter-examples?  Or did you mean all
text anywhere, including outside of Emacs?

> and straight quotes (though of course not perfect) are a better
> choice for plain text intended for users.

There you go again.  You think they are a better choice; OK, we got that.

> There is longstanding precedent for using straight quotes in some Emacs
> news items. It's not just etc/NEWS before the recent round of changes;
> for example, the NEWS entry for Emacs 1.4 (in etc/NEWS.1-17), circa
> 1985, uses straight quotes for its only quoted string, presumably to
> distinguish the quotes from the grave accents elsewhere in the entry.

Holy cow!  Talk about disingenous.  Anyone else bother to check
this?  Dunno what you mean by "its only quoted string", but I
found only the following 5 such occurrences, and these are
clearly all _mistakes_, especially when looked at in context:

1. Rmail command '>' goes to the last message.
2. included and letter 'F' had 
3. the new code letter 'D' which
4. It is like 'f' except
5. The Lisp function 'function' now exists.

When you see something like this it's pretty clear that 'F' is a typo:

 The value should be a string containing `-' followed by letters.
 The letter `l' had better be included and letter 'F' had better
 be excluded!

I checked quickly, so I'll grant that you might be able to find
one or two other occurrences.  I counted 5, but let's say there
might be as many as 10.

Now let's see how many occurrences of `...' there are.  I count
345.  That's 70 to 1.  Or 35 to 1, if we give you the benefit
of the doubt.

> It shouldn't be a problem for users if NEWS uses straight quotes
> from here on out.

Yeah, sure. "From here on out." Setting another precedent, are we?



  reply	other threads:[~2016-03-16  0:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160314154123.2684.74715@vcs.savannah.gnu.org>
     [not found] ` <E1afUcV-0000iS-4N@vcs.savannah.gnu.org>
2016-03-14 15:44   ` [Emacs-diffs] emacs-25 26b56dc: Fix some single quotes in documentation John Wiegley
2016-03-14 16:31     ` Paul Eggert
2016-03-14 16:39       ` John Wiegley
2016-03-14 16:42         ` Dmitry Gutov
2016-03-14 17:19           ` Clément Pit--Claudel
2016-03-14 17:37             ` Dmitry Gutov
2016-03-14 17:53               ` Kaushal Modi
2016-03-14 18:10                 ` Drew Adams
2016-03-14 18:32           ` Paul Eggert
2016-03-14 18:43             ` Eli Zaretskii
2016-03-14 18:48               ` John Wiegley
2016-03-14 18:58                 ` Eli Zaretskii
2016-03-14 18:45             ` John Wiegley
2016-03-14 19:14               ` Paul Eggert
2016-03-14 19:29                 ` John Wiegley
2016-03-14 20:47                   ` Paul Eggert
2016-03-14 20:50                     ` John Wiegley
2016-03-15  0:30                       ` Paul Eggert
2016-03-15 22:21                         ` John Wiegley
2016-03-15 23:13                         ` Lars Magne Ingebrigtsen
2016-03-15 23:56                           ` Drew Adams
2016-03-16  0:11                           ` Paul Eggert
2016-03-16  0:52                             ` Drew Adams [this message]
2016-03-16  8:16                               ` John Wiegley
2016-03-16 17:55                               ` Paul Eggert
2016-03-16 21:26                                 ` Drew Adams
2016-03-16 23:37                                   ` Paul Eggert
2016-03-16 23:41                                     ` Drew Adams
2016-03-14 20:56                     ` Alan Mackenzie
2016-03-15  0:39                       ` Paul Eggert
2016-03-14 18:50             ` Kaushal Modi
2016-03-14 19:11             ` Dmitry Gutov
2016-03-14 19:16             ` Drew Adams
2016-03-14 19:39               ` John Wiegley
2016-03-14 19:47                 ` Dmitry Gutov
2016-03-14 17:03       ` Eli Zaretskii
2016-03-14 18:24         ` Paul Eggert
2016-03-14 18:42           ` 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=124b0893-9ed5-4532-8ade-619609973117@default \
    --to=drew.adams@oracle.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    /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).