From: Ihor Radchenko <yantar92@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 70696@debbugs.gnu.org
Subject: bug#70696: [PATCH] Autoload `re-disassemble'
Date: Thu, 02 May 2024 14:26:47 +0000 [thread overview]
Message-ID: <87ikzw9tnc.fsf@localhost> (raw)
In-Reply-To: <jwva5l8bb16.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The functionality was designed under the assumption that it's used for
> the benefit of those working on the regexp engine.
>
> AFAIK you're not working on the regexp engine (are you?), so I'm curious
> what you're using this function for: maybe it is more generally useful
> than we thought and it deserves to be less hidden.
I saw the NEWS entry:
** New function 're-disassemble' to see the innards of a regexp.
If you compiled with '--enable-checking', you can use this to help debug
either your regexp performance problems or the regexp engine.
and I noticed the "regexp performance" part, which Org mode sometimes
struggles with (we just had a bug report recently where the problem lies
with way too complex regexp that makes things slow)
So, I tried to play around with this new function, attempting to see if
it can be of any use to simplify regular expressions. (Spoiler: alas, it
is not by itself useful, without knowing the internals of Emacs regexp
engine.)
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-05-02 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 11:28 bug#70696: [PATCH] Autoload `re-disassemble' Ihor Radchenko
2024-05-02 10:13 ` Eli Zaretskii
2024-05-02 10:21 ` Mattias Engdegård
2024-05-02 10:27 ` Ihor Radchenko
2024-05-02 11:19 ` Eli Zaretskii
2024-05-02 11:25 ` Ihor Radchenko
2024-05-02 13:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-02 14:26 ` Ihor Radchenko [this message]
2024-05-02 14:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-04 11:40 ` 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=87ikzw9tnc.fsf@localhost \
--to=yantar92@posteo.net \
--cc=70696@debbugs.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).