From: Phil Hagelberg <phil@hagelb.org>
To: 2577@emacsbugs.donarmstrong.com
Subject: bug#2577: 23.0.91; startup.el should choose .emacs ahead of .emacs.elc if .emacs is newer
Date: Fri, 06 Mar 2009 12:04:42 -0800 [thread overview]
Message-ID: <87mybya04l.fsf@hagelb.org> (raw)
The specific failure is this:
A user keeps his entire .emacs.d in an SCM system. This includes not
only his personal customizations, (which would hardly benefit from
compilation) but third-party libraries that haven't made it into Emacs
proper yet. These third-party libraries are byte-compiled in every
checkout of the user's .emacs.d, which span multiple machines.
One of these libraries gets a bug fixed, so he installs the update and
checks it in. Now he moves to another machine that has his dotfiles
checked out, and he pulls in the update, but it's ignored in favour of
the out-of-date .elc file.
Everyone I know who uses Emacs seriously keeps their .emacs.d in an SCM
as well as third-party libraries, so I don't consider this much of an
edge case.
Ideally a flag would exist that could instruct Emacs to ignore
out-of-date .elc files. I understand this is not appropriate to submit
during a feature freeze, but saying it's not a problem is not helpful.
-Phil
next reply other threads:[~2009-03-06 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 20:04 Phil Hagelberg [this message]
2009-03-06 20:23 ` bug#2577: 23.0.91; startup.el should choose .emacs ahead of .emacs.elc if .emacs is newer Glenn Morris
2009-03-06 20:30 ` Processed: " Emacs bug Tracking System
2009-03-07 14:24 ` Leo
-- strict thread matches above, loose matches on Subject: below --
2009-03-05 8:44 Alex
2009-03-05 16:49 ` Stefan Monnier
2009-03-06 10:18 ` Alex
2009-03-06 10:55 ` Eli Zaretskii
2009-03-06 13:37 ` Jason Rumney
2009-03-07 22:08 ` Alex
2009-03-07 23:11 ` Stefan Monnier
2009-03-08 1:06 ` Lennart Borgman
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=87mybya04l.fsf@hagelb.org \
--to=phil@hagelb.org \
--cc=2577@emacsbugs.donarmstrong.com \
/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).