From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: rms@gnu.org
Cc: lekktu@gmail.com, 2061@emacsbugs.donarmstrong.com, bgoodr@gmail.com
Subject: bug#2061: 23.0.60; Add preference to force load of Elisp files when they are newer than corresponding byte-compiled file
Date: Tue, 03 Feb 2009 16:07:32 -0500 [thread overview]
Message-ID: <jwvbptjqlh5.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <E1LUI3t-0003qF-2X@fencepost.gnu.org> (Richard M. Stallman's message of "Tue, 03 Feb 2009 04:59:21 -0500")
> If so, I wonder if the right solution is to do something special when loading
> a file for `require' in compilation.
Indeed, that's what I do in my local branch, where the bytecompiler's
handling of require gives precedence to the .el files over the .elc files.
> Perhaps offer to compile them?
It needs to work in batch mode. And byte-compiling them can easily fall
into circularities.
Stefan
next prev parent reply other threads:[~2009-02-03 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 0:49 bug#2061: 23.0.60; Add preference to force load of Elisp files when they are newer than corresponding byte-compiled file Stefan Monnier
2009-02-02 18:56 ` Juanma Barranquero
2009-02-03 21:08 ` bug#2061: 23.0.60; Add preference to force load of Elisp files Stefan Monnier
2013-12-18 3:24 ` Glenn Morris
2009-02-03 9:59 ` bug#2061: 23.0.60; Add preference to force load of Elisp files when they are newer than corresponding byte-compiled file Richard M Stallman
2009-02-03 21:07 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-26 2:19 Brent Goodrick
2009-01-26 4:08 ` Eli Zaretskii
2009-01-27 15:08 ` Brent Goodrick
2009-01-26 8:45 ` Juanma Barranquero
2009-01-27 15:54 ` Brent Goodrick
2009-01-28 2:06 ` Juanma Barranquero
2009-01-28 8:29 ` Kevin Rodgers
2009-02-02 16:07 ` Brent Goodrick
2009-01-26 16:31 ` Richard M Stallman
2009-01-27 15:56 ` Brent Goodrick
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvbptjqlh5.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=2061@emacsbugs.donarmstrong.com \
--cc=bgoodr@gmail.com \
--cc=lekktu@gmail.com \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.