Re: context coloring leaks out of verbatim environment

* Ulrich Scholz (2005-02-28) writes:

>> Hm, you could try it by starting Emacs with `emacs -q' which will at
>> least inhibit your user init file from being loaded while still
>> loading the site init file (which obviously sets some Debian-specific
>> defaults).
>
> OK, after `emacs -q file.tex' I get the LaTeX menu.

Uh, did you do the same with `emacs -q -no-site-file'?  That means,
did you specify the file name on the command line as well?  Then it is
obvious why you did not get into AUCTeX's LaTeX mode because it did
not have a chance to associate itself with .tex files.

If you want to test with `-no-site-file' you have to start Emacs with
`emacs -q -no-site-file' and without providing a file name at the
command line.  When Emacs is running you do `M-: (require 'tex-site)
RET' and `M-x global-font-lock-mode RET'.  _After_ that you can load a
LaTeX file.

> Then I did `M-: (require
> 'tex-site)'

You seem to have told the Debian package to load AUCTeX via the site
init file if you get a "LaTeX" menu right away.  In this case the
require statement does not do anything.

> and `M-x global-font-lock-mode RET'.  The coloring appears and
> does not leak.

Good to hear. (c:

> If I find time the next week I try to track down the problematic portion of my
> initialization files.
>
>> But I am a bit stumped that requiring tex-site and loading a LaTeX
>> file after that did not result in an error.  Do you have several
>> AUCTeX installations?
>
> Not that I know of.  How do I check this?  I used the standard Debian tools to
> install emacs.

Usually you can check stuff like this with `M-x list-load-path-shadows
RET'.  But AFAICS it is not necessary in your case.  The cause that
you got presented with Emacs' built-in LaTeX mode was that you
specified a file name on the command line and did not give AUCTeX the
chance to be loaded.  And because AUCTeX seems to be installed
correctly, the `(require 'tex-site)' did not result in an error.

-- 
Ralf