From: Eli Zaretskii <eliz@gnu.org>
To: Alex <alex@bennee.com>, 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:55:06 +0200 [thread overview]
Message-ID: <uocwencol.fsf@gnu.org> (raw)
In-Reply-To: <20090306101854.GW28813@bennee.com>
> Date: Fri, 6 Mar 2009 11:18:54 +0100
> From: Alex <alex@bennee.com>
> Cc: emacs-pretest-bug@gnu.org, 2577@emacsbugs.donarmstrong.com
>
> On Thu, Mar 05, 2009 at 11:49:42AM -0500, Stefan Monnier wrote:
> > > Currently startup.el warns if .emacs.elc is newer than .emacs however
> > > this hides subtle bugs if people don't carefully watch their logs/mode
> > > line during startup. Although many people have clever auto-compile
> > > magic every tiome they save .emacs this often break down when they
> > > pull in updates via SCMs.
> >
> > I think that if people compile their .emacs they get what they ask for.
>
> That's not very helpful.
Maybe not, but it isn't clear, at least not to me, what alternative
behavior do you suggest. How about spelling it out?
If this is your suggestion:
> It should still warn, but by default it should go with the newest
> version.
then I doubt that it will fly, as Emacs does not do this with any
other Lisp file. It always warns and goes with the .elc file.
next prev parent reply other threads:[~2009-03-06 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 8:44 bug#2577: 23.0.91; startup.el should choose .emacs ahead of .emacs.elc if .emacs is newer Alex
2009-03-05 16:49 ` Stefan Monnier
2009-03-06 10:18 ` Alex
2009-03-06 10:55 ` Eli Zaretskii [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-03-06 20:04 Phil Hagelberg
2009-03-06 20:23 ` Glenn Morris
2009-03-07 14:24 ` Leo
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=uocwencol.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=2577@emacsbugs.donarmstrong.com \
--cc=alex@bennee.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 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.