puzzled with load-path entries - where do they come from when .emacs is empty?

puzzled with load-path entries - where do they come from when .emacs is empty?

[Mirko]

Hello,

I am using emacs 22.1 on windows & I am puzzled with the components of
load-path: where are they coming from:

Even if I completely comment out all of my .emacs, and my
EMACSLOADPATH is empty, when I start up emacs, my load-path is full of
stuff: slime, planner, muse, auctex,... that I use.  But since I
commented all of the code in .emacs where did that stuff come from?
Again, my .emacs is completely commented out.

Thanks,

Mirko

Re: puzzled with load-path entries - where do they come from when .emacs is empty?

[Mirko]

On Nov 10, 12:10 pm, Mirko <mvuko...@nycap.rr.com> wrote:
> Hello,
>
> I am using emacs 22.1 on windows & I am puzzled with the components of
> load-path: where are they coming from:
>
> Even if I completely comment out all of my .emacs, and my
> EMACSLOADPATH is empty, when I start up emacs, my load-path is full of
> stuff: slime, planner, muse, auctex,... that I use.  But since I
> commented all of the code in .emacs where did that stuff come from?
> Again, my .emacs is completely commented out.
>
> Thanks,
>
> Mirko

As additional info, here is my *Message* buffer
("E:\\program-files\\emacs-22.1\\bin\\emacs.exe" "--debug-init")
Loading encoded-kb...done
Loading e:/program-files/emacs-22.1/site-lisp/tex-site.el
(source)...done
Loading debug...done
Entering debugger...
Loading help-mode...done

Emacs is loading auctex' tex-site.  No idea why.

Also, I checked, and there is no ~/.emacs.elc file.

Still puzzled,

Mirko

Re: puzzled with load-path entries - where do they come from when .emacs is empty?

[Mirko]

On Nov 10, 1:59 pm, Mirko <mvuko...@nycap.rr.com> wrote:
> On Nov 10, 12:10 pm, Mirko <mvuko...@nycap.rr.com> wrote:
>
> > Hello,
>
> > I am using emacs 22.1 on windows & I am puzzled with the components of
> > load-path: where are they coming from:
>
> > Even if I completely comment out all of my .emacs, and my
> > EMACSLOADPATH is empty, when I start up emacs, my load-path is full of
> > stuff: slime, planner, muse, auctex,... that I use.  But since I
> > commented all of the code in .emacs where did that stuff come from?
> > Again, my .emacs is completely commented out.
>
> > Thanks,
>
> > Mirko
>
> As additional info, here is my *Message* buffer
> ("E:\\program-files\\emacs-22.1\\bin\\emacs.exe" "--debug-init")
> Loading encoded-kb...done
> Loading e:/program-files/emacs-22.1/site-lisp/tex-site.el
> (source)...done
> Loading debug...done
> Entering debugger...
> Loading help-mode...done
>
> Emacs is loading auctex' tex-site.  No idea why.
>
> Also, I checked, and there is no ~/.emacs.elc file.
>
> Still puzzled,
>
> Mirko

I found site-lisp/site-start.d with auctex.el and preview-latex.el.
That explains the auctex message during startup.  But still no clue as
to where load-path gets preloaded.

Actually, could it be that emacs populates load-path automatically
based on the contents of the site-lisp directory?  That would explain
everything.

Thanks to all that helped :-)

Mirko

Re: puzzled with load-path entries - where do they come from when .emacs is empty?

[Xah]

Mirko <mvuko...@nycap.rr.com> wrote:
> I am using emacs 22.1 on windows & I am puzzled with the components of
> load-path: where are they coming from:

> Even if I completely comment out all of my .emacs, and my
> EMACSLOADPATH is empty, when I start up emacs, my load-path is full of
> stuff: slime, planner, muse, auctex,... that I use.  But since I
> commented all of the code in .emacs where did that stuff come from?
> Again, my .emacs is completely commented out.
> ...
> I found site-lisp/site-start.d with auctex.el and preview-latex.el.
> That explains the auctex message during startup.  But still no clue as
> to where load-path gets preloaded.
>
> Actually, could it be that emacs populates load-path automatically
> based on the contents of the site-lisp directory?  That would explain
> everything.

basically all langs, e.g. perl, java, python, php, mathematica,
provides you with a default load path, so that basic functionalities
are available.

if emacs doesn't provide you with a default path, all the basic major
modes, c, java, perl, shell, dired ... and probably most of
fundamental working of emacs will break.

At a user level, if you want absolutely the minimal stuff in load
path, start emacs with --no-site-file --no-init-file. You'll probably
still see entries in load path though. If for some reason you simply
don't want any, you can set it to empty and see what is the effect, or
hack emacs's source.

  Xah
∑ http://xahlee.org/

☄

Re: puzzled with load-path entries - where do they come from when .emacs is empty?

[Mirko]

On Nov 10, 7:08 pm, Xah <xah...@gmail.com> wrote:
> Mirko <mvuko...@nycap.rr.com> wrote:
> > I am using emacs 22.1 on windows & I am puzzled with the components of
> > load-path: where are they coming from:
> > Even if I completely comment out all of my .emacs, and my
> > EMACSLOADPATH is empty, when I start up emacs, my load-path is full of
> > stuff: slime, planner, muse, auctex,... that I use.  But since I
> > commented all of the code in .emacs where did that stuff come from?
> > Again, my .emacs is completely commented out.
> > ...
> > I found site-lisp/site-start.d with auctex.el and preview-latex.el.
> > That explains the auctex message during startup.  But still no clue as
> > to where load-path gets preloaded.
>
> > Actually, could it be that emacs populates load-path automatically
> > based on the contents of the site-lisp directory?  That would explain
> > everything.
>
> basically all langs, e.g. perl, java, python, php, mathematica,
> provides you with a default load path, so that basic functionalities
> are available.
>
> if emacs doesn't provide you with a default path, all the basic major
> modes, c, java, perl, shell, dired ... and probably most of
> fundamental working of emacs will break.
>
> At a user level, if you want absolutely the minimal stuff in load
> path, start emacs with --no-site-file --no-init-file. You'll probably
> still see entries in load path though. If for some reason you simply
> don't want any, you can set it to empty and see what is the effect, or
> hack emacs's source.
>
>   Xah
> ∑http://xahlee.org/
>
> ☄

Xah, Kevin,

Thanks for the pointers

Mirko

Re: puzzled with load-path entries - where do they come from when .emacs is empty?

[Kevin Rodgers]

Mirko wrote:
> I found site-lisp/site-start.d with auctex.el and preview-latex.el.
> That explains the auctex message during startup.  But still no clue as
> to where load-path gets preloaded.
> 
> Actually, could it be that emacs populates load-path automatically
> based on the contents of the site-lisp directory?  That would explain
> everything.

See the "Startup Summary" node of the Emacs Lisp manual:

| The order of operations performed (in `startup.el') by Emacs when it is
| started up is as follows:
|
|   1. It adds subdirectories to `load-path', by running the file named
|     `subdirs.el' in each directory in the list.  Normally this file
|      adds the directory's subdirectories to the list, and these will be
|      scanned in their turn.  The files `subdirs.el' are normally
|      generated automatically by Emacs installation.

To see how load-path is initialized while building Emacs, see the
Makefile (itself generated from Makefile.in by configure):

| # Where to install the lisp files distributed with
| # Emacs.  This includes the Emacs version, so that the
| # lisp files for different versions of Emacs will install
| # themselves in separate directories.
| lispdir=${datadir}/emacs/${version}/lisp
|
| # Directories Emacs should search for lisp files specific
| # to this site (i.e. customizations), before consulting
| # ${lispdir}.  This should be a colon-separated list of
| # directories.
| 
locallisppath=${datadir}/emacs/${version}/site-lisp:${datadir}/emacs/site-lisp
|
| # Where Emacs will search to find its lisp files.  Before
| # changing this, check to see if your purpose wouldn't
| # better be served by changing locallisppath.  This
| # should be a colon-separated list of directories.
| lisppath=${locallisppath}:${lispdir}:${datadir}/emacs/${version}/leim


-- 
Kevin Rodgers
Denver, Colorado, USA