unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Fixing post-self-insert-hook.
Date: Fri, 17 Sep 2021 22:45:19 +0100	[thread overview]
Message-ID: <874kaiev0w.fsf@gmail.com> (raw)
In-Reply-To: <YUUAVqxOgXq0+MwA@ACM> (Alan Mackenzie's message of "Fri, 17 Sep 2021 20:53:42 +0000")

Alan Mackenzie <acm@muc.de> writes:

> Actually, it was just 111, not 293.  Sorry.

Are you familiar with the GitHub platform? It's averse to the FSF and
software freedom in some ways, but it also hosts much source code and
has a moderately useful search tool for code "in the wild".

Here's a pertinent search "self-insert-command":

   https://github.com/search?p=6&q=self-insert-command&type=Code

It lists almost 83 thousand hits in emacs lisp, many in forks of Emacs,
and many more in user configurations or packages we don't know about.  I
found it curious that it doesn't take much page turning to find users
undoing problematic bindings in c-mode-base-map back to
self-insert-command.  I do this myself but seem to be joined by others.

I find also interesting how, given such pervasive usage of
self-insert-command and reasonable popularity of electric-pair-mode (8k
hits in the same search), the on-default of electric-indent-mode, etc,
our bug tracker isn't overflowing with bug reports about electric modes,
post-self-insert-hook or their "undefined behaviour" or "race condition"
(as you describe them).  The only ones I know about are about cc-mode.el

Best regards,
João

PS: If people know of electric-pair-mode related bugs for other major
modes (_not cc-mode_), please forward them to me for analysis.  Thanks
in advance.



  reply	other threads:[~2021-09-17 21:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 19:37 Fixing post-self-insert-hook Alan Mackenzie
2021-09-17 20:04 ` Stefan Monnier
2021-09-17 20:53   ` Alan Mackenzie
2021-09-17 21:45     ` João Távora [this message]
2021-09-18  6:08       ` tomas
2021-09-18  8:44         ` João Távora
2021-09-18 14:15     ` Stefan Monnier
2021-09-18 15:56       ` Alan Mackenzie
2021-09-18 18:03         ` Stefan Monnier
     [not found]         ` <CALDnm52z_8HyqdC92nrMgzOMOOq48h2MQ4pjbROBOsdm5N_cJg@mail.gmail.com>
2021-09-18 22:55           ` João Távora
2021-09-19 12:14             ` Alan Mackenzie
2021-09-19 12:36               ` João Távora
2021-09-19 12:59               ` Stefan Monnier
2021-09-19 14:57                 ` Alan Mackenzie
2021-09-19 20:20                   ` Stefan Monnier
2021-09-17 20:15 ` João Távora
2021-09-17 20:35   ` Alan Mackenzie
2021-09-17 20:48     ` João Távora
2021-09-18  5:59     ` Eli Zaretskii
2021-09-18  9:41       ` Alan Mackenzie
2021-09-18  5:50 ` Eli Zaretskii
2021-09-18  9:57   ` Alan Mackenzie
2021-09-18 11:04     ` 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=874kaiev0w.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --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).