From: "Eddward DeVilla" <eddward@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: proposal: defconst/defcustom org-tags-regexp
Date: Thu, 19 Jul 2007 11:14:12 -0500 [thread overview]
Message-ID: <b71b18520707190914u6bbae5afjfce6abfba4edc54f@mail.gmail.com> (raw)
In-Reply-To: <20ed9633cd33f9824fae1ae6c47c9159@science.uva.nl>
On 7/19/07, Carsten Dominik <dominik@science.uva.nl> wrote:
>
> On Jul 19, 2007, at 15:08, Eddward DeVilla wrote:
> > Does emacs let you manually compile a regular expression? If so, it
> > might be possible to recompile REs when ever they change.
>
> This is not the issue. Yes, Emacs compiles regular expressions
> whenever necessary. However, consider the following loop:
I meant, could you store a compiled RE in a variable and use the
compiled form. Then manually recompile them if someone changes the
uncompiled RE string. This assumes you can store the compiled RE and
that there is a hook in custom to let you know it has changed. We'd
probably want to have a function the regenerates all of org's REs and
allow others to hook into that to recompile their own REs.
On the other hand, I just went digging through the elisp manual and
I didn't see anything that would generate a compiled RE to be stored
and (re)used later. Bummer. Maybe if I get bored, I might see if
performance is ok with the REs factored out, but I don't suspect I
would get good results.
Edd
next prev parent reply other threads:[~2007-07-19 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 13:21 proposal: defconst/defcustom org-tags-regexp Adam Spiers
2007-07-18 21:24 ` Carsten Dominik
2007-07-19 13:08 ` Eddward DeVilla
2007-07-19 15:08 ` Carsten Dominik
2007-07-19 16:14 ` Eddward DeVilla [this message]
2007-07-20 15:05 ` Adam Spiers
[not found] ` <931245f7aaa24436377e537552f1beab@science.uva.nl>
2007-09-01 11:01 ` Adam Spiers
2007-09-02 7:30 ` Carsten Dominik
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=b71b18520707190914u6bbae5afjfce6abfba4edc54f@mail.gmail.com \
--to=eddward@gmail.com \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
/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).