Path: utzoo!utgpu!watmath!clyde!ima!think!rlk
From: rlk@think.com (Robert Krawitz)
Newsgroups: comp.emacs
Subject: Re: startup.el
Message-ID: <35065@think.UUCP>
Date: 3 Jan 89 16:21:49 GMT
References: <2225@imagine.PAWL.RPI.EDU>
Sender: news@think.UUCP
Reply-To: rlk@think.com (Robert Krawitz)
Organization: Thinking Machines Corp., Cambridge MA
Lines: 30
In-reply-to: Dave Lawrence

In article <2225@imagine.PAWL.RPI.EDU>, Dave Lawrence writes:
]I honestly don't understand why .emacs is not the last elisp file loaded ...
]it only seems natural that a user should be able to undo things that
]he doesn't like which are done by another start-up file.  I'd call it
]a "programming oversight" rather than a bug.

Emacs does the correct thing by loading your .emacs file first.  If
term-file-prefix is nil, emacs will not attempt to load the terminal
initialization file.

What you should do is load whatever terminal setup code you wish (you
can crib code from startup.el if you want to load the terminal init
file and overload it with your stuff) and set term-file-prefix to nil.
This will inhibit loading the terminal setup file.

Note that if your .emacs file is loaded after the terminal init file,
the latter could mutate your environment in undesirable ways before
you can do anything about it.  The way the startup sequence works now,
you have first and last crack at your environment.

]Does anyone have a suggestion?  I'd rather not have to move all of
]the terminal code from startup.el (and then disable processing of
]it in startup.el) because disk-space is very tight here -- every
]page is important.

There's about 5 lines of code involved.
-- 
harvard >>>>>>  |	Robert Krawitz <rlk@think.com>	245 First St.
bloom-beacon >  |think!rlk	(postmaster)		Cambridge, MA  02141
topaz >>>>>>>>  .	Thinking Machines Corp.		(617)876-1111