Uwe Brauer writes:
> No. Did you set TeX-auto-private to something other than
`nil'? If
Nope, its value is:
| `TeX-style-private' is a variable declared in Lisp.
|
| Value: ("/home/oub/tex/sty/auto/")
I'm getting confused. In the previous mail you mentioned both
TeX-auto-private and TeX-style-private, but claimed that
TeX-auto-private is missing. Now you're saying TeX-style-private is
missing, and its value is named "auto".
I guess that XEmacs isn't lying when you copy the output from C-h v,
but overall it's very hard to be confident of the reliability of your
reports.
,----
| `TeX-style-path' is a variable declared in Lisp.
| -- loaded from "tex"
Do you "(require 'tex)" before you set (eg, in custom.el) the
TeX-*-private variables? Traditionally, and probably in GNU Emacs,
custom was loaded before init, but there was a rash of people who had
reasons to load init before custom (typically they wanted to share
their init and custom files among different Emacsen and/or platforms,
and needed to compute values that were used by custom defaults), so
XEmacs switched the order about 10 years ago, because it's trivial to
load custom at the beginning of init when the default is to load
custom afterward, but essentially impossible to unload custom once
it's loaded.
What you should do is move the (require 'tex) late in init and put a
call to (load "/path/to/.xemacs/custom") *before* that. (It actually
probably doesn't matter where you put the `load' call as long as it's
before the (require 'tex).)
(Technically, to be perfectly sure you don't screw things up by
loading custom twice, you do
(progn
(load "/path/to/.xemacs/custom" t t)
(setq custom-file nil)
(add-hook 'after-init-hook
(lambda () (setq custom-file "/path/to/.xemacs/custom"))))
), but that's likely overkill.
Tassilo suspects that it is the (add-to-list 'path file t)
call which might cause the problem, and has changed it.
I don't think that's very likely. If that were the problem, I'd
expect you to get `nil' as the value of TeX-style-path. There's no
reason why the code you showed would treat TeX-*-private variables
specially, except that they are not given values until after you load
"tex".
Ie, if you comment out the defvar or defcustoms defining the
TeX-*-private variables, I bet you'll get a error of "unbound
variable" at init time.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta