From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: phst@google.com, p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: [PATCH] Disable electric quotes in the Emacs codebase.
Date: Thu, 03 Jan 2019 15:48:28 +0200 [thread overview]
Message-ID: <83va353l8z.fsf@gnu.org> (raw)
In-Reply-To: <ede35c63-983f-1658-bae9-dc715f0bb654@cs.ucla.edu> (message from Paul Eggert on Wed, 2 Jan 2019 13:58:14 -0800)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 2 Jan 2019 13:58:14 -0800
> Cc: Philipp Stephani <phst@google.com>
>
> Philipp Stephani wrote:
> > + (electric-quote-comment . nil)
> > + (electric-quote-string . nil)))
>
> Why is this needed? Electric quote mode isn't on by default.
It would be good to hear the rationale, yes.
I can think about one: to void inserting curved quotes into Emacs
messages and doc strings. Are there other reasons?
> I find it helpful to use electric-quote mode for some files, and if there's a
> need to disable it it'd be better to limit it to files where it should be
> disabled rather than have a blanket prohibition.
Maybe we should indeed do this only in Lisp and C modes. (In Lisp we
could allow this in comments, though.)
Paul, can you tell in which files you find electric quote mode
helpful?
Thanks.
next prev parent reply other threads:[~2019-01-03 13:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 21:21 [PATCH] Disable electric quotes in the Emacs codebase Philipp Stephani
2019-01-02 21:58 ` Paul Eggert
2019-01-02 22:16 ` Dmitry Gutov
2019-01-03 13:48 ` Eli Zaretskii [this message]
2019-01-03 19:14 ` Paul Eggert
2019-01-03 19:34 ` Eli Zaretskii
2019-01-06 0:40 ` Philipp Stephani
2019-01-06 2:12 ` Paul Eggert
2019-01-06 3:38 ` Eli Zaretskii
2019-01-06 21:34 ` Philipp Stephani
2019-01-06 21:58 ` [PATCH] Disable electric quotes for most files " Philipp Stephani
2019-01-09 15:30 ` Eli Zaretskii
2019-01-15 0:40 ` Philipp Stephani
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=83va353l8z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=phst@google.com \
/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.