Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!bbn!jr@bbn.com
From: jr@bbn.com (John Robinson)
Newsgroups: comp.emacs
Subject: Re: .emacs (was re: loadst dies)
Summary: it can be compiled
Message-ID: <40936@bbn.COM>
Date: 5 Jun 89 17:28:38 GMT
References: <8906051517.AA01192@dsys.ncsl.nist.gov>
Sender: news@bbn.COM
Reply-To: jr@bbn.com (John Robinson)
Organization: BBN Systems and Technologies Corporation, Cambridge MA
Lines: 29
In-reply-to: rbj@dsys.ncsl.nist.GOV (Root Boy Jim)

In article <8906051517.AA01192@dsys.ncsl.nist.gov>, rbj@dsys (Root Boy Jim) writes:
>? From: att!mcdchg!rave!lynn@cis.ohio-state.edu  (Lynn D. Newton)
>?							  I did a
>? lot of work on my .emacs (248 lines -- too long to quote).
>
>Yes, but not specifically on your problem. I merely wish to point
>out that 248 lines in your .emacs is too much. Remember that .emacs
>is not byte compiled, it is much more efficient to put only (load)'s
>in there, plus maybe a few variable settings. Put function definitions
>in your lisp directory and byte compile them.

... or make a hard or symbolic link from .emacs to .emacs.elc, and put
all your stuff in your .emacs.el.  Remember to byte-compile the latter
when you change it.  (The byte-compiler preserves links to the .elc
file).  I use the following csh alias to avoid carrying the
byte-compiler code around in my running emacs:

  alias elc 'emacs -batch -f batch-byte-compile \!*'

setup.el calls, essentially,

  (load "~/.emacs" t t t)

The last t suppresses load's normal behavior of trying .emacs.elc,
then .emacs.el, then .emacs.  Anyone know why this is the choice,
other than speed?  (Obviously, would obviate the link).
--
/jr, nee John Robinson   What a waste it is to lose one's mind--or not
jr@bbn.com or bbn!jr      to have a mind.  How true that is. -Dan Quayle