From: Jim Porter <jporterbugs@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 49518@debbugs.gnu.org
Subject: bug#49518: 28.0.50; electric-pair-mode skip-self fails for single-quotes in python-mode
Date: Sun, 11 Jul 2021 10:34:19 -0700 [thread overview]
Message-ID: <CANh=_JGh9iW2ohct3-p_k7T4a_dHvC=Ao4kWqkB68yGkRvzLyA@mail.gmail.com> (raw)
In-Reply-To: <877dhxp8wn.fsf@gmx.net>
On Sun, Jul 11, 2021 at 1:11 AM Stephen Berman <stephen.berman@gmx.net> wrote:
>
> One thing that's kinda nice about the current behavior of typing
> single-quote in python-mode is that if you type it three times in a row
> you get '''|''', so it's ready for typing a multiple string. This
> doesn't happen with double-quote, and after setting
> electric-pair-text-syntax-table to python-mode-syntax-table it doesn't
> happen any more with single-quote.
That's true, and I've been working on a patch to make that behavior
more robust. The code for that is in
`python-electric-pair-string-delimiter', but I think an improved
implementation of that would depend on how this bug is fixed. I have a
local patch that works for me, but it depends on the other
electric-pair settings I use, so it couldn't merge as-is.
In particular, it would need to take into account the various possible
settings for `electric-pair-skip-self', since with that set to nil,
I'd generally expect `python-electric-pair-string-delimiter' to be a
no-op (we should already have three quote characters after point, so
no need to insert more).
next prev parent reply other threads:[~2021-07-11 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 1:32 bug#49518: 28.0.50; electric-pair-mode skip-self fails for single-quotes in python-mode Jim Porter
2021-07-11 8:11 ` Stephen Berman
2021-07-11 17:34 ` Jim Porter [this message]
2021-09-18 12:55 ` Daniel Fleischer
2021-09-18 16:56 ` Jim Porter
2021-09-18 23:43 ` João Távora
2021-09-19 0:20 ` João Távora
2021-09-19 1:55 ` Jim Porter
2021-09-19 10:44 ` João Távora
2021-09-19 16:35 ` João Távora
2021-09-21 9:59 ` João Távora
2021-09-22 20:04 ` Jim Porter
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='CANh=_JGh9iW2ohct3-p_k7T4a_dHvC=Ao4kWqkB68yGkRvzLyA@mail.gmail.com' \
--to=jporterbugs@gmail.com \
--cc=49518@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/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).