From: Arash Esbati <arash@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71337@debbugs.gnu.org, stephen.berman@gmx.net,
joaotavora@gmail.com, monnier@iro.umontreal.ca
Subject: bug#71337: 30.0.50; `electric-pair-mode' and custom keybinding
Date: Tue, 04 Jun 2024 14:33:54 +0200 [thread overview]
Message-ID: <m2mso028gd.fsf@macmutant.fritz.box> (raw)
In-Reply-To: <81C90874-2077-4358-A611-BDC94B98287E@gnu.org> (Eli Zaretskii's message of "Tue, 04 Jun 2024 12:24:59 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> It looks like Arash made the mistake of being the first one, ever, of
> invoking self-insert-command from Lisp with 2nd arg non-nil, and
> turning on electric-pair-mode on top of that.
Sorry for that :-)
> When self-insert-command is called with 2 args, it uses the 2nd arg as
> the character to insert, but it does NOT overwrite last-command-event
> with that character. So post-self-insert-hook sees the wrong event
> and rightfully barfs.
Maybe I missed something, but is there a canonical way to achieve what I
want? Background is that on macOS with German keyboard layout, I have
to hit 'Shift-Option-7' for a backslash which really bugs me.
> I think internal_self_insert should overwrite last-command-event or
> something, if we want to support this kind of scenario. Stefan, WDYT?
It seems I'm not the only one with this idea:
https://medium.com/@chasinglogic/defying-your-keyboard-with-elisp-366ab9cec85c
So supporting this kind of scenario could make sense.
Best, Arash
next prev parent reply other threads:[~2024-06-04 12:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 12:40 bug#71337: 30.0.50; `electric-pair-mode' and custom keybinding Arash Esbati
2024-06-03 13:50 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04 5:53 ` Arash Esbati
2024-06-04 7:30 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04 7:37 ` João Távora
2024-06-04 8:08 ` João Távora
2024-06-04 8:18 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04 14:52 ` Eli Zaretskii
2024-06-04 9:24 ` Eli Zaretskii
2024-06-04 10:09 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04 10:49 ` João Távora
2024-06-04 11:04 ` Eli Zaretskii
2024-06-04 14:56 ` Eli Zaretskii
2024-06-04 15:43 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04 12:33 ` Arash Esbati [this message]
2024-06-04 13:36 ` João Távora
2024-06-04 14:09 ` Arash Esbati
2024-06-04 14:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-15 8:10 ` Eli Zaretskii
2024-06-16 10:42 ` Arash Esbati
2024-06-04 8:09 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=m2mso028gd.fsf@macmutant.fritz.box \
--to=arash@gnu.org \
--cc=71337@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
--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).