From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: FIXED!! Re: Clarification of eval-after-load [was: Problem mit symlinks, locate-library and load-history]
Date: Sun, 21 May 2006 22:39:05 -0400 [thread overview]
Message-ID: <E1Fi0K1-0002yU-4F@fencepost.gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1060520194822.293C-100000@acm.acm> (message from Alan Mackenzie on Sun, 21 May 2006 09:39:50 +0000 (GMT))
>I don't like the use of regexp-opt. Can you get rid of that?
I'm not quite sure exactly what you don't like about it.
I don't like having to load it in order for Emacs to start up.
I am sure this can be implemented some other way.
. Thus this regexp is now only built once for each eval-after-load call,
and regexp-opt.elc doesn't need to be preloaded.
That is somewhat of an improvement; but given how limited your use
of these regexps is, can't you construct them without regexp-opt?
I think that won't really be hard.
HOWEVER, regexp-opt.elc WASN'T BEING LOADED AT emacs START UP, thus
causing an error, because .../lisp/emacs-lisp isn't on load-path at emacs
start up.
Avoiding the use of regexp-opt would eliminate the need for this, too.
Please try that; I think you will find it is not very hard.
next prev parent reply other threads:[~2006-05-22 2:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 21:11 Clarification of eval-after-load [was: Problem mit symlinks, locate-library and load-history] Alan Mackenzie
2006-05-11 16:46 ` Stuart D. Herring
2006-05-11 17:19 ` Alan Mackenzie
2006-05-11 17:46 ` Stuart D. Herring
2006-05-11 21:44 ` Alan Mackenzie
2006-05-12 4:15 ` Richard Stallman
2006-05-14 11:07 ` FIXED!! " Alan Mackenzie
2006-05-15 5:13 ` Richard Stallman
2006-05-21 9:39 ` Alan Mackenzie
2006-05-22 2:39 ` Richard Stallman [this message]
2006-05-23 17:21 ` Alan Mackenzie
2006-05-23 17:51 ` Andreas Schwab
2006-05-23 20:10 ` Alan Mackenzie
2006-05-23 20:58 ` FIXED!! Re: Clarification of eval-after-load Stefan Monnier
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=E1Fi0K1-0002yU-4F@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.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).