From: Eli Zaretskii <eliz@gnu.org>
To: Joseph Turner <joseph@breatheoutbreathe.in>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 72437@debbugs.gnu.org
Subject: bug#72437: Unexpected behavior when inserting with prefix arg in electric-pair-mode
Date: Sat, 03 Aug 2024 12:12:06 +0300 [thread overview]
Message-ID: <86h6c2ug0p.fsf@gnu.org> (raw)
In-Reply-To: <87le1edqqm.fsf@breatheoutbreathe.in> (message from Joseph Turner on Sat, 03 Aug 2024 00:12:33 -0700)
> Cc: eliz@gnu.org
> From: Joseph Turner <joseph@breatheoutbreathe.in>
> Date: Sat, 03 Aug 2024 00:12:33 -0700
>
> Migrated from this thread on the devel mailing list:
>
> https://yhetil.org/emacs-devel/86ikwiumza.fsf@gnu.org/T/#t
>
>
> On Emacs 29.4, with emacs -Q
>
> Turn on electric-pair-mode
>
> (electric-pair-mode +1)
>
> Then press "C-2 ("
>
> Expected result:
>
> Either (()) or ()()
>
> Actual result:
>
> (()
>
>
> I noticed the unexpected behavior when attempting to surround some text
> with multiple braces in order to create Anki flashcards.
>
> More or less, I wanted to go from "foo" to "{{foo}}", and I thought
> perhaps that with the whole word selected, pressing "C-2 {" would DTRT.
>
> In general, I'm not sure whether "{}{}" or "{{}}"is more useful or
> expected, but I suspect both are better than "{{}".
Making it produce "{}{}" is relatively easy: we just need to call the
post-self-insert-hook for each of the ARG inserted characters. OTOH,
to produce "{{}}" we'd probably need to rewrite the
electric-pair-mode's hook function, but I have no idea how to rewrite
it to do that.
Stefan, any suggestions?
next prev parent reply other threads:[~2024-08-03 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 7:12 bug#72437: Unexpected behavior when inserting with prefix arg in electric-pair-mode Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-03 9:12 ` Eli Zaretskii [this message]
2024-08-03 11:04 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-03 15:40 ` Eli Zaretskii
2024-08-03 18:18 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-03 18:46 ` Eli Zaretskii
2024-08-14 1:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-14 5:07 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-14 11:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-17 6:28 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 5:14 ` Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-14 0:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-16 21:22 ` João Távora
2024-08-17 6:08 ` Eli Zaretskii
2024-08-17 9:30 ` João Távora
2024-08-17 14:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-17 14:21 ` Eli Zaretskii
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=86h6c2ug0p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72437@debbugs.gnu.org \
--cc=joseph@breatheoutbreathe.in \
--cc=monnier@iro.umontreal.ca \
/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).