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>, Paul Eggert <eggert@cs.ucla.edu>
Cc: drew.adams@oracle.com, emacs-devel@gnu.org
Subject: RE: how to turn off automatic curly-quoting?
Date: Mon, 3 Aug 2015 08:48:37 -0700 (PDT)	[thread overview]
Message-ID: <ec07a835-5027-4c33-a5b1-c8afc12a4a76@default> (raw)
In-Reply-To: <<83a8u8v1zk.fsf@gnu.org>>

> > > Also, why is the name about "translation"?  Shouldn't
> > > this option just be about what style is used for quoting
> > > Emacs terms?
> >
> > That point has also been made.  I changed the name to 'text-quoting-style'
> > in the attached patch.  Although it's just a name, it does have uses
> > outside help buffers so at least the 'help' part of the name was misleading.
> > Other Emacs packages (e.g., coreutils) use "quoting-style" but that's too
> > generic for Emacs which has other interpretation of the word "quoting".
> 
> How about 'symbol-quoting-style'?  Isn't that more accurate than
> 'text-quoting-style'?

Definitely.  But this "quoting" is used not only for symbols but also
for Lisp (and other language?) sexps generally.  It is also used for
key sequences.  And I've seen other uses too - cross-refs, file names,
or URLs, perhaps?

`sexp-quoting-style' is better than `symbol-quoting-style' is (much!)
better than `text-quoting-style', which is quite misleading.

What about just `quoting-style'?

But again, this is not at all about ordinary text quoting (which is
why we should not be using ordinary curly quotes for this at all).



  parent reply	other threads:[~2015-08-03 15:48 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
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 [this message]
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=ec07a835-5027-4c33-a5b1-c8afc12a4a76@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).