🚀 go-pugleaf

I really appreciate all the help everyone's sent, but most of the replies
don't answer the question, which was:

In article <#01G_0e+1@cs.psu.edu> jim@math.psu.edu (Jim Duncan) writes:

> Why can't I get it to set the path from site-init.el?

Lance Brown <brown@cs.utk.edu> sent this helpful note:

> If the build runs emacs in -batch mode then that is your problem.  There is
> a "bug" in the file startup.el that puts a temporary 
> 
> (let (load-path ...)  blah)
> 
> form around the code that actually loads and interprets any .el or .elc
> files being loaded into the emacs.

However, there is no "(let (load-path" in startup.el that I can find (this
is 18.57, by the way).  In fact, load-path is not referenced anywhere in
startup.el.  From looking at lread.c, it appears that a rather blatant
assumption is made that no one would ever want to have more than one
directory in the default load-path.

You can't just add an extra path to paths.h, because each would have to be a
null-terminated string.  A colon-delimited set is no good either.  I forgot
to mention in my previous posting that I tried all sorts of creative things
via paths.h (but maybe I didn't hit the magic permutation).

So, back to the original question:  Why doesn't the load-path get set
correctly from site-init.el?  What's going on here?

Thanks to all who reply (and replied).  I *do* appreciate the help.

	Jim



--
    Jim Duncan <jim@math.psu.edu> Penn State Math Dept Systems Administrator
 "[A computer is] like an Old Testament god, with a lot of rules and no mercy."
						Joseph Campbell