From: Drew Adams <drew.adams@oracle.com>
To: 21472@debbugs.gnu.org
Subject: bug#21472: 25.0.50; REGRESSION: (emacs) `Coding Systems' uses curly quotes for Lisp strings
Date: Sun, 13 Sep 2015 08:45:01 -0700 (PDT) [thread overview]
Message-ID: <c7ebc07d-51c9-4d10-9238-d42b0b3845b7@default> (raw)
Emacs Info manuals have long used double-quotes for two things:
* Setting off terms that are defined (e.g., glossary terms).
(This is presumably the case for the occurrence of "codepages"
in this same node.)
* Programming strings - e.g. Lisp strings (including file-name strings).
In (emacs) `Coding Sytems', at least, it seems that Curly-Quote Mania
has struck another nasty blow:
In addition to converting various representations of non-ASCII
characters, a coding system can perform end-of-line conversion. Emacs
handles three different conventions for how to separate lines in a file:
newline ("unix"), carriage-return linefeed ("dos"), and just
carriage-return ("mac").
Why curly double-quotes here? Either those quoted names are supposed
to be Lisp strings or they are proper names. In the latter case they
should not be quoted at all, and they should be properly capitalized.
In the former case (which is what I'm guessing is meant), plain ASCII
double-quote chars should be used.
Please don't confuse users this way, and make them guess what is meant.
Get it straight, please.
Plain ASCII double-quote chars should always be used for strings.
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2015-08-16 on LEG570
Bzr revision: f7ee23e587b01f179284b5554c67d579a2def676
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --host=3Di686-pc-mingw32 --enable-checking=3Dyes,glyphs'
next reply other threads:[~2015-09-13 15:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 15:45 Drew Adams [this message]
2015-09-13 20:07 ` bug#21472: 25.0.50; REGRESSION: (emacs) `Coding Systems' uses curly quotes for Lisp strings Eli Zaretskii
2015-09-13 21:11 ` Drew Adams
2015-09-14 6:24 ` Eli Zaretskii
2015-09-14 14:08 ` Richard Stallman
2015-09-15 15:57 ` Paul Eggert
2015-09-15 16:00 ` Eli Zaretskii
2015-09-15 16:22 ` Paul Eggert
2015-09-15 23:48 ` Drew Adams
2015-09-15 16:26 ` Eli Zaretskii
2015-09-15 19:15 ` Paul Eggert
2015-09-15 23:48 ` Drew Adams
2015-09-16 6:56 ` Eli Zaretskii
2015-09-16 7:32 ` Eli Zaretskii
2015-09-16 7:48 ` Paul Eggert
2015-09-16 10:02 ` Eli Zaretskii
2015-09-15 23:48 ` Drew Adams
2015-09-15 23:48 ` Drew Adams
2015-09-16 7:23 ` Eli Zaretskii
2015-09-16 7:49 ` Paul Eggert
2015-09-16 10:07 ` Eli Zaretskii
2015-09-16 15:31 ` Paul Eggert
2015-09-16 17:18 ` Eli Zaretskii
2015-09-16 18:27 ` Paul Eggert
2015-09-16 18:34 ` Eli Zaretskii
2015-09-16 20:31 ` Paul Eggert
2015-09-17 4:46 ` Eli Zaretskii
2015-09-17 5:21 ` Paul Eggert
2015-09-17 6:03 ` Eli Zaretskii
2015-09-17 7:21 ` Paul Eggert
2015-09-17 7:35 ` Eli Zaretskii
[not found] ` <<831tdz8yf8.fsf@gnu.org>
2015-09-15 23:48 ` Drew Adams
[not found] <<c7ebc07d-51c9-4d10-9238-d42b0b3845b7@default>
[not found] ` <<83vbbe9j7k.fsf@gnu.org>
[not found] ` <<661f3a80-cdaf-47f0-a096-4be744409150@default>
[not found] ` <<83pp1la58d.fsf@gnu.org>
2015-09-14 13:51 ` Drew Adams
2015-09-15 0:21 ` Richard Stallman
[not found] ` <<55F83FDF.2070202@cs.ucla.edu>
[not found] ` <<3aa1fafa-ed4d-4935-8a3e-cae7d0842c5f@default>
[not found] ` <<83r3ly7rpd.fsf@gnu.org>
2015-09-16 15:16 ` Drew Adams
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=c7ebc07d-51c9-4d10-9238-d42b0b3845b7@default \
--to=drew.adams@oracle.com \
--cc=21472@debbugs.gnu.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).