From: Timothy <orgmode@tec.tecosaur.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Max Nikulin <manikulin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Radio links work only in small numbers
Date: Tue, 20 Dec 2022 11:21:20 +0800 [thread overview]
Message-ID: <87bknyah7t.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <87a63qx9au.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Hi All,
> It’s not like we cannot fix this by splitting the regexp manually into
> prefix tree.
>
> The question is performance though.
For reference, I ran into this issue with Org Glossary, and did exactly this:
see <https://github.com/tecosaur/org-glossary/blob/master/org-glossary.el#L804>.
I sort all the strings being matched with `string<' and then create clumps of ~800
terms and then search with the constructed regex for each clump in turn.
Obviously this has a performance impact, but it seems to work well enough, and
working slower is clearly better than not working at all.
All the best,
Timothy
--
Timothy (‘tecosaur’/‘TEC’), 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/tec>.
next prev parent reply other threads:[~2022-12-20 3:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 23:10 Radio links work only in small numbers Rudolf Adamkovič
2022-12-14 8:30 ` Ihor Radchenko
2022-12-14 15:29 ` Rudolf Adamkovič
2022-12-14 15:47 ` Max Nikulin
2022-12-14 16:02 ` Ihor Radchenko
2022-12-20 3:21 ` Timothy [this message]
2022-12-20 1:00 ` Rudolf Adamkovič
2022-12-28 9:46 ` Daniel Clemente
2024-02-19 9:26 ` Ihor Radchenko
2024-02-28 16:33 ` nobiot
2024-02-28 17:14 ` Ihor Radchenko
2024-02-28 22:18 ` Noboru Ota
2024-02-29 11:11 ` Ihor Radchenko
2024-02-29 16:47 ` Noboru Ota
2024-02-29 17:21 ` Ihor Radchenko
2024-02-29 17:44 ` Noboru Ota
2024-04-04 20:20 ` Rudolf Adamkovič
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bknyah7t.fsf@tec.tecosaur.net \
--to=orgmode@tec.tecosaur.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=yantar92@posteo.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/org-mode.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).