[AUCTeX] help with auctex

[François Patte]

Bonjour,

I have just updated my auctex from elpa to auctex-11.89.5.

I would like to know:

1- How does emacs know the new path to auctex-11.89.5 as nothing has
changed in my .emacs file ((add-to-list 'load-path
"~/.emacs.d/elpa/auctex-11.88.6") is still there but emacs uses now:
~/.emacs.d/elpa/auctex-11.89.5/)

2- In a previous version of auctex, if I used the local variables to
define the TeX-master file with \documentclass{beamer}, for instance:

%%% Local Variables:
%%% mode: latex
%%% TeX-master: "15-11-2016-beamer"
%%% End:

at the end of a file loaded in the master file 15-11-2016-beamer.tex by
an \input or \include command, then the beamer macros were loaded and I
could use the keyboard shortcut C-c C-e to set a beamer environments in
the "slave" file.

This does not work now....

How can I recover this feature?

Thank you.

[Jorge A. Alfaro-Murillo]

Hi, François.

Post by François Patte
1- How does emacs know the new path to auctex-11.89.5 as nothing
has changed in my .emacs file ((add-to-list 'load-path
"~/.emacs.d/elpa/auctex-11.88.6") is still there but emacs uses
now: ~/.emacs.d/elpa/auctex-11.89.5/)

Probably package-initialize is called in your init file after that
add-to-list. If you do not a call to package-initialize in your
init file, it gets added to it automatically by package.el.

If you install packages with elpa you do not need the add-to-list,
package-initialize takes care of adjusting the load-path and using
require in the latest installed version of each package.

Best,

[jfbu]

Post by Jorge A. Alfaro-Murillo
Hi, François.

1- How does emacs know the new path to auctex-11.89.5 as nothing has changed in my .emacs file ((add-to-list 'load-path "~/.emacs.d/elpa/auctex-11.88.6") is still there but emacs uses now: ~/.emacs.d/elpa/auctex-11.89.5/)

Probably package-initialize is called in your init file after that add-to-list. If you do not a call to package-initialize in your init file, it gets added to it automatically by package.el.

Just a side note: I find this a bit bad, because in my case I have an .emacs which is used as a dispatch depending on the version of Emacs in use. Hence the forcefully added package-initialize needed to be manually corrected for use only in the correct branches.

Best,

JF

Post by Jorge A. Alfaro-Murillo
If you install packages with elpa you do not need the add-to-list, package-initialize takes care of adjusting the load-path and using require in the latest installed version of each package.
Best,

[Jorge A. Alfaro-Murillo]

Post by jfbu

Post by Jorge A. Alfaro-Murillo

Post by François Patte
1- How does emacs know the new path to auctex-11.89.5 as
nothing has changed in my .emacs file ((add-to-list 'load-path
"~/.emacs.d/elpa/auctex-11.88.6") is still there but emacs
uses now: ~/.emacs.d/elpa/auctex-11.89.5/)

Probably package-initialize is called in your init file after
that add-to-list. If you do not a call to package-initialize in
your init file, it gets added to it automatically by
package.el.

Just a side note: I find this a bit bad, because in my case I
have an .emacs which is used as a dispatch depending on the
version of Emacs in use. Hence the forcefully added
package-initialize needed to be manually corrected for use only
in the correct branches.

If the first line of your .emacs is the call to package-initialize
commented out:

;(package-initialize)

then package.el doesn't try to add that line again.

[jfbu]

Post by Jorge A. Alfaro-Murillo

Post by jfbu

Post by Jorge A. Alfaro-Murillo

1- How does emacs know the new path to auctex-11.89.5 as nothing has changed in my .emacs file ((add-to-list 'load-path "~/.emacs.d/elpa/auctex-11.88.6") is still there but emacs uses now: ~/.emacs.d/elpa/auctex-11.89.5/)

Probably package-initialize is called in your init file after that add-to-list. If you do not a call to package-initialize in your init file, it gets added to it automatically by package.el.

Just a side note: I find this a bit bad, because in my case I have an .emacs which is used as a dispatch depending on the version of Emacs in use. Hence the forcefully added package-initialize needed to be manually corrected for use only in the correct branches.

;(package-initialize)
then package.el doesn't try to add that line again.

Yes, fortunately ! this is why I was only half-complaining ;-)

Jean-François