From: Alex <alex@bennee.com>
To: Jason Rumney <jasonr@gnu.org>
Cc: 2577@emacsbugs.donarmstrong.com
Subject: bug#2577: 23.0.91; startup.el should choose .emacs ahead of .emacs.elc if .emacs is newer
Date: Sat, 7 Mar 2009 23:08:11 +0100 [thread overview]
Message-ID: <20090307220811.GX28813@bennee.com> (raw)
In-Reply-To: <49B12731.8060104@gnu.org>
On Fri, Mar 06, 2009 at 09:37:53PM +0800, Jason Rumney wrote:
> Alex wrote:
>>> I think that if people compile their .emacs they get what they ask for.
>>>
>>
>> That's not very helpful.
>
> For you, perhaps not. But we have discussed this on emacs-devel numerous
> times in the past, and every time it has been clear that different
> people have different opinions. Many people consider lisp source to be
> "work in progress" until they compile it, and do not want Emacs to load
> it by default if there is a compiled version around. The compromise is
> to issue a warning.
>
> If you have a problem remembering to compile your .emacs, then either
> delete the .emacs.elc file and stop compiling it, or investigate one of
> the solutions that people have come up with to compile it
automatically.
Typically it's pulling in a later version from an SCM that the warning
case trips up on, as the doesn't trip the compile-on-save hook that
most people use to auto compile .emacs.
As Emacs is a configurable editor would adding a variable to control
this behaviour be the way forward? A lot of people do run their
configs out of an SCM these days. Someone else suggested maybe being
able to use def advice to modify the behaviour which might make any
work-arounds less hacky but I'm not sure what this would entail for
the core code.
--
Alex, homepage: http://www.bennee.com/~alex/
Tax and title extra.
next prev parent reply other threads:[~2009-03-07 22:08 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
2009-03-06 13:37 ` Jason Rumney
2009-03-07 22:08 ` Alex [this message]
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
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=20090307220811.GX28813@bennee.com \
--to=alex@bennee.com \
--cc=2577@emacsbugs.donarmstrong.com \
--cc=jasonr@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 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).