From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: How to opt out of curly-quote spamming altogether?
Date: Mon, 24 Aug 2015 18:22:38 +0300 [thread overview]
Message-ID: <83fv38hfsx.fsf@gnu.org> (raw)
In-Reply-To: <a4c77735-a9de-400e-88f2-243c66e24836@default>
> Date: Sun, 23 Aug 2015 21:16:18 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> `help-quote-translation' does seem to prevent curly quotes in
> *Help* buffers, so at least there's that. But I'm looking for
> a switch to turn this virus OFF everywhere - to return to
> Classic Emacs. Surely such a simple ON/OFF switch exists?
It doesn't. What you see in Info is literal characters generated when
the documentation is built during the Emacs build process. So, to
change that, you will have to regenerate the documentation, telling
makeinfo not to produce Unicode characters there.
Alternatively, you can set up your standard-display-table to display
those characters as their ASCII equivalents.
next prev parent reply other threads:[~2015-08-24 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 4:16 How to opt out of curly-quote spamming altogether? Drew Adams
2015-08-24 15:22 ` Eli Zaretskii [this message]
2015-08-24 15:26 ` Paul Eggert
2015-08-24 17:06 ` Drew Adams
[not found] <<a4c77735-a9de-400e-88f2-243c66e24836@default>
[not found] ` <<83fv38hfsx.fsf@gnu.org>
2015-08-24 16:34 ` Drew Adams
2015-08-24 16:45 ` Eli Zaretskii
2015-08-24 17:09 ` Paul Eggert
2015-08-24 17:29 ` Drew Adams
2015-08-24 18:44 ` Paul Eggert
[not found] ` <<c8408881-dddb-4661-9e7f-6ec42d9bf5fa@default>
[not found] ` <<837fokhby1.fsf@gnu.org>
2015-08-24 17:06 ` Drew Adams
2015-08-24 17:25 ` Eli Zaretskii
[not found] <<c1f42565-e538-49e6-b246-07e43dab673a@default>
[not found] ` <<834mjoha4r.fsf@gnu.org>
2015-08-24 17:57 ` Drew Adams
2015-08-24 18:05 ` Eli Zaretskii
2015-08-24 18:36 ` David Kastrup
2015-08-24 21:44 ` Drew Adams
2015-08-25 4:25 ` David Kastrup
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fv38hfsx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.