From: Richard M Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
2061@emacsbugs.donarmstrong.com
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 04:59:21 -0500 [thread overview]
Message-ID: <E1LUI3t-0003qF-2X@fencepost.gnu.org> (raw)
In-Reply-To: <jwvocxk3ecq.fsf@iro.umontreal.ca> (message from Stefan Monnier on Mon, 26 Jan 2009 19:49:20 -0500)
A common case for me is "bzr pull" or "cvs update" or "tla star-merge"
to bring in new changes. I don't look at all the Elisp files brought in
so byte-compile-file is not convenient, and byte-compilation often leads
to odd results because the `require's read the old .elc files.
Are you saying that in this case you would want to load the .el files
instead?
If so, I wonder if the right solution is to do something special when loading
a file for `require' in compilation. Perhaps offer to compile them?
next prev parent reply other threads:[~2009-02-03 9:59 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 ` Richard M Stallman [this message]
2009-02-03 21:07 ` bug#2061: 23.0.60; Add preference to force load of Elisp files when they are newer than corresponding byte-compiled file Stefan Monnier
-- 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
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=E1LUI3t-0003qF-2X@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=2061@emacsbugs.donarmstrong.com \
--cc=bgoodr@gmail.com \
--cc=lekktu@gmail.com \
--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).