From: Drew Adams <drew.adams@oracle.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: how to turn off automatic curly-quoting?
Date: Mon, 3 Aug 2015 10:31:49 -0700 (PDT) [thread overview]
Message-ID: <7197418a-d51f-4d0e-a01c-188d27a0f21f@default> (raw)
In-Reply-To: <55BF9B8C.6010300@cs.ucla.edu>
> > How about 'symbol-quoting-style'? Isn't that more accurate than
> > 'text-quoting-style'?
>
> No, as the style is used for quoting pretty much anything, not just
> symbols. It can quote symbols, node references, file names,
Yes.
> and various English phrases such as ‘C source code’.
The latter is a mistake (a bug) IMHO. I assume you are referring
to the fact that `C-h f' shows this:
forward-char is an interactive built-in function in ‘C source code’.
The quoted phrase here is ordinary English. It happens to be a link.
Whoever added that linked phrase should not have quoted it in any way.
Do you know of other occurrences of quoting ordinary text with `...'
in Emacs? I doubt it, but there might be one or two such bugs. It
happens that people updating the manual sometimes use "..." or `...'
inappropriately. But it is rare.
The kind of "quoting" we are talking about (which was `...') should
_not at all be used for ordinary text quoting_. It should be limited
to what is shown in most doc systems using a monospaced font. The
best example is showing code fragments inline, i.e., in the middle of
a sentence of ordinary text.
> And once we change the ‘message’ function to use the style, it'll
> quote even more things.
That would be quite misguided - a big mistake, IMHO. But please be
specific about what change you have in mind here.
Think ordinary docs, and how they talk about code fragments. They
typically use a monospace font for that. Or sometimes they use
highlighting. They do *not* use quote marks. And most importantly,
they do not use the same thing they use for quoting ordinary text.
If you start using ‘...’ (curly quotes) for everything under the
sun then you will lose the ability to distinguish things. And you
will confuse readers.
next prev parent reply other threads:[~2015-08-03 17:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<36f6e67e-45d9-4eca-8302-ad9a06d138f1@default>
[not found] ` <<83fv41v6fh.fsf@gnu.org>
2015-08-02 21:47 ` how to turn off automatic curly-quoting? Drew Adams
2015-08-02 23:06 ` Paul Eggert
2015-08-02 23:57 ` Artur Malabarba
2015-08-03 0:11 ` Paul Eggert
2015-08-03 0:02 ` Drew Adams
2015-08-03 0:40 ` Paul Eggert
2015-08-03 2:28 ` Drew Adams
2015-08-03 5:11 ` Paul Eggert
2015-08-03 15:13 ` Eli Zaretskii
2015-08-03 16:49 ` Paul Eggert
2015-08-03 17:31 ` Drew Adams [this message]
2015-08-03 18:59 ` Paul Eggert
2015-08-03 19:33 ` Drew Adams
2015-08-03 21:06 ` Paul Eggert
2015-08-03 19:14 ` Eli Zaretskii
[not found] ` <<5681a732-5741-4f56-b3d7-cb1edb739d32@default>
[not found] ` <<55BEA291.70402@cs.ucla.edu>
[not found] ` <<83a8u8v1zk.fsf@gnu.org>
2015-08-03 15:48 ` Drew Adams
2015-08-03 16:14 ` Eli Zaretskii
2015-08-02 17:18 Drew Adams
2015-08-02 19:25 ` Eli Zaretskii
2015-08-02 19:46 ` Paul Eggert
2015-08-02 20:11 ` Drew Adams
2015-08-02 20:26 ` Paul Eggert
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=7197418a-d51f-4d0e-a01c-188d27a0f21f@default \
--to=drew.adams@oracle.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).