unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
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 11:44:17 -0700	[thread overview]
Message-ID: <55DB6601.8040406@cs.ucla.edu> (raw)
In-Reply-To: <971f6dbd-dee5-4c58-8a67-a001a3d540c3@default>

Drew Adams wrote:
> You decide how much benefit it is to users?  How about letting
> them decide, themselves?

You can rebuild the Info files yourself, using Texinfo 4 or with some Texinfo 5 
option that I don't recall offhand.  So you have a choice.

Shipping two versions of Emacs, or even two versions of the info files, would 
complicate things for maintainers and distributors and users, and this burden 
would outweigh any minor benefit.



  reply	other threads:[~2015-08-24 18:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<a4c77735-a9de-400e-88f2-243c66e24836@default>
     [not found] ` <<83fv38hfsx.fsf@gnu.org>
2015-08-24 16:34   ` How to opt out of curly-quote spamming altogether? 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 [this message]
     [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
2015-08-24  4:16 Drew Adams
2015-08-24 15:22 ` Eli Zaretskii
2015-08-24 15:26 ` Paul Eggert
2015-08-24 17:06   ` 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=55DB6601.8040406@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --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 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).