From: Philipp Stephani <p.stephani2@gmail.com>
To: 23387@debbugs.gnu.org, eggert@cs.ucla.edu
Cc: 23387-done@debbugs.gnu.org
Subject: bug#23387: 25.0.93; Unicode quote inserted in Python mode outside of strings
Date: Tue, 03 May 2016 20:44:27 +0000 [thread overview]
Message-ID: <CAArVCkRj6arn-hh5bit6EtqBXqK2P+F7c0C2sLnT7pK8Dzoi1Q@mail.gmail.com> (raw)
In-Reply-To: <a2876c56-af94-7cd5-02f5-b2c8fc640bda@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
Paul Eggert <eggert@cs.ucla.edu> schrieb am Mo., 2. Mai 2016 um 18:05 Uhr:
> Thanks for the bug report and patch, but I ran into a problem with the
> patch. Suppose I do this:
>
> emacs -Q
> M-x electric-quote-mode
> M-x customize-variable RET electric-quote-string, set it to t, save
> M-x python-mode
> 'abc'
>
> That is, I type apostrophe-a-b-c-apostrophe in Python mode. With the
> patch, the buffer will contain:
>
> 'abc’
>
> The opening apostrophe is OK, but the closing apostrophe is considered
> to be inside a string so it is transmogrified into a right single
> quotation mark. A Python programmer would want both to be apostrophes.
>
I'm not sure, I think if a user has electric-quote-string enabled, that's
the behavior they want, because it's inside a string. However, I can see
that both approaches are valid. There is probably no good way that would
work in all circumstances.
[-- Attachment #2: Type: text/html, Size: 1243 bytes --]
prev parent reply other threads:[~2016-05-03 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 14:14 bug#23387: 25.0.93; Unicode quote inserted in Python mode outside of strings Philipp Stephani
2016-04-28 17:11 ` Philipp Stephani
2016-04-28 17:22 ` Philipp Stephani
2016-04-30 11:59 ` Philipp Stephani
2016-05-02 16:04 ` Paul Eggert
2016-05-03 20:44 ` Philipp Stephani [this message]
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=CAArVCkRj6arn-hh5bit6EtqBXqK2P+F7c0C2sLnT7pK8Dzoi1Q@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=23387-done@debbugs.gnu.org \
--cc=23387@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.