Re: path problem in auctex

Uwe Brauer <[email protected]>
Newsgroups gmane.emacs.xemacs.beta
Message-ID <[email protected]>
>> "Stephen" == Stephen J Turnbull <[email protected]> writes:

   > Uwe Brauer writes:

   > 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.

Ok, I should not write reports when I am overworked, sorry. 

I try to restart from scratch. I have deleted the relevant parts in my
custom file and restarted xemacs.

The relevant parts of my .emacs file look like that


(load-file "~/xemacs/init/xemacs_init.el") 
(setq custom-file "/home/oub/xemacs/init/custom-init.el")

In the xemacs_init.el file there is a require to tex, well actually to
(require 'tex-site) which does all the necessary initializing.

Now all my auctex variables, which I have configured via custom, work
without problems.


So first to the value  of the  TeX-style-path variable
,----
| `TeX-style-path' is a variable declared in Lisp.
|   -- loaded from "tex"
| 
| Value: ("/usr/local/var/auctex/" "/usr/local/share/xemacs/xemacs-packages/etc/auctex/style" "/home/oub/.emacs.d/auctex/auto" "/home/oub/.emacs.d/auctex/style" "auto" "style")
| 
| Documentation:
| List of directories to search for AUCTeX style files.
| Per default the list is built from the values of the variables
| `TeX-auto-global', `TeX-style-global', `TeX-auto-private',
| `TeX-style-private', `TeX-auto-local', and `TeX-style-local'.
`----

Now to the value  of TeX-style-private variable
,----
| 
| `TeX-style-private' is a variable declared in Lisp.
|   -- loaded from "tex"
| 
| Value: ("/home/oub/.emacs.d/auctex/style")
| 
| Documentation:
| List of directories containing hand-generated AUCTeX style files.
| 
| These correspond to the personal TeX macros.
`----

This is the standard setting. So since my style files do not sit in 
"/home/oub/.emacs.d/auctex/style" I change this variable (either by
substituting its value or my adding a new directory (it does not matter);
Say I add a directory via customize and its value is now:

,----
| `TeX-style-private' is a variable declared in Lisp.
|   -- loaded from "tex"
| 
| Value: ("/home/oub/.emacs.d/auctex/style" "/home/oub/tex/sty/auto")
| 
| Documentation:
| List of directories containing hand-generated AUCTeX style files.
| 
| These correspond to the personal TeX macros.
`----

However the value of TeX-style-path has *NOT* changed:
,----
| `TeX-style-path' is a variable declared in Lisp.
|   -- loaded from "tex"
| 
| Value: ("/usr/local/var/auctex/" "/usr/local/share/xemacs/xemacs-packages/etc/auctex/style" "/home/oub/.emacs.d/auctex/auto" "/home/oub/.emacs.d/auctex/style" "auto" "style")
| 
| Documentation:
| List of directories to search for AUCTeX style files.
| Per default the list is built from the values of the variables
| `TeX-auto-global', `TeX-style-global', `TeX-auto-private',
| `TeX-style-private', `TeX-auto-local', and `TeX-style-local'.
`----

I swear: I do the *same* steps in GNU Emacs (with different init files
in different directories) and the value of TeX-style-path changes.



   > 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).)


Well the customization of all the other AUCTeX variable work, so your
advice sounds strange but I will try it out.

Result:

I does not help. Actually the problem on a practical level has an easy
fix, just customize directly the variable TeX-style-path variable.

I find it just curious that in xemacs the modification of the value of
TeX-style-private is not passed to TeX-style-path.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.