unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, 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 10:06:31 -0700 (PDT)	[thread overview]
Message-ID: <c1f42565-e538-49e6-b246-07e43dab673a@default> (raw)
In-Reply-To: <<837fokhby1.fsf@gnu.org>>

> > That's horrible.  Users should be able to control this, easily.
> 
> Why?  We don't have easy controls for displaying one character as
> another.  Why should these characters be different?

This is not about "displaying one character as another."  It is
about choosing how to present inline code fragments.  It is not
about substituting for literal curly quotes everwhere, as I made
clear.

> > I don't see this problem in a Windows binary from 2014-11-30.  The
> > regression was apparently introduced to the Windows builds between
> > then and 2014-12-29.
> 
> It's the question of which version of Texinfo was used for producing
> the docs.  The defaults in Texinfo changed recently, independently
> of Emacs development.

Defaults?  So Emacs has a choice?

> > A display-table hack would presumably change all uses of a curly
> > quote.
> 
> A display table can be specific to a buffer or a window.  See the
> ELisp manual for more about that.

I don't see how that would help anyone.  It's too late, once the
curly quotes are hard-coded in the output.  There is no reasonable
way for a user at that point to tell Emacs which occurrences
represent presentation of inline code and which really belong
as literal curly quotes.

> But it was you that asked for a switch that changed them
> _everywhere_, which is why I suggested standard-display-table,
> which is global.

Disingenuous.  You know full well what I'm talking about: undoing
the use of curly quotes to replace `...'.  And yes, that everywhere.
But certainly not _replacing_ all occurrences of curly quotes,
including any that have nothing to do with inline code (`...').

> > That's not appropriate - it is only the code-"quoting"
> > uses that need to be changable/configurable by a user.
> 
> What is "code-'quoting'"?  An Info manual is not code, it's mostly
> text, but you still wanted these characters changed there.

The use of `...' has primarily been to set off inline code fragments
from the surrounding text.

It has also been used sometimes for URLs, file names, and some links,
but those uses are arguably inappropriate.  Use whatever phrase you
like, but you know, I think, that I am referring to the replacement
of `...' by wrapping with curly quotes, and only that.



  parent reply	other threads:[~2015-08-24 17:06 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
     [not found]   ` <<c8408881-dddb-4661-9e7f-6ec42d9bf5fa@default>
     [not found]     ` <<837fokhby1.fsf@gnu.org>
2015-08-24 17:06       ` Drew Adams [this message]
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=c1f42565-e538-49e6-b246-07e43dab673a@default \
    --to=drew.adams@oracle.com \
    --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).