From: David Abrahams <dave@boost-consulting.com>
Cc: Juri Linkov <juri@jurta.org>, emacs-devel@gnu.org
Subject: Re: bug in save-some-buffers or diff.el?
Date: Thu, 23 Oct 2003 15:47:08 -0400 [thread overview]
Message-ID: <u1xt3zqgz.fsf@boost-consulting.com> (raw)
In-Reply-To: <E1ACkLT-0004iy-Uc@fencepost.gnu.org> (Richard Stallman's message of "Thu, 23 Oct 2003 14:38:03 -0400")
Richard Stallman <rms@gnu.org> writes:
> BTW, I'm sure that current behavior of `load' is wrong. It always
> tries to load .elc file first, even if it's older than .el. But often
> it causes too much trouble after updating .el files. There are many
> reasons why this happens: user forgets to recompile updated .el files,
> something goes wrong in the make process, etc. Yes, `load' reports
> a warning, but usually this warning goes unnoticed, which results in
> broken functionality. Instead, `load' should load the newest of .el
> or .elc files, and report the same warning as a simple reminder to
> recompile updated .el files to execute them faster.
>
> the current behavior is necessary and will not be changed.
Care to explain? Python users seem to like the one Juri proposed, so
it works well at least in some contexts.
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2003-10-23 19:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 0:07 bug in save-some-buffers or diff.el? David Abrahams
2003-10-22 8:38 ` Juri Linkov
2003-10-22 9:35 ` David Abrahams
2003-10-22 12:52 ` Stefan Monnier
2003-10-22 15:22 ` David Abrahams
2003-10-22 14:35 ` Juri Linkov
2003-10-22 16:28 ` David Abrahams
2003-10-22 16:34 ` Kevin Rodgers
2003-10-22 17:52 ` Eli Zaretskii
2003-10-23 4:53 ` Juri Linkov
2003-10-23 6:06 ` Eli Zaretskii
2003-10-23 8:00 ` Juri Linkov
2003-10-24 14:52 ` Eli Zaretskii
2003-10-23 18:38 ` Richard Stallman
2003-10-23 19:47 ` David Abrahams [this message]
2003-10-24 10:41 ` Richard Stallman
2003-10-27 17:44 ` emacshear (was: bug in save-some-buffers or diff.el?) Juri Linkov
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=u1xt3zqgz.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).