Hi Rene,
Rene jl...@yahoo.com writes:
Achim Gratz Stromeko at nexgo.de writes:
Line 4 of `org-autoloads.el in org/elpa package.
Since this file is created by package manager this is probably how it
adds Org to the load path, don't you think?
What I notice is that for elpa packages that
Bastien bzg at gnu.org writes:
The way elpa works, it automatically adds packages to `load-path'. There is
therefore no need to have such a line
(add-to-list 'load-path (or (file-name-directory #$) (car load-path)))
in the `package-autoloads.el file.
Where is this file?
Line 4
Rene writes:
The way elpa works, it automatically adds packages to `load-path'. There
is
therefore no need to have such a line
(add-to-list 'load-path (or (file-name-directory #$) (car load-path)))
in the `package-autoloads.el file.
Where is this file?
Line 4 of
Achim Gratz Stromeko at nexgo.de writes:
Line 4 of `org-autoloads.el in org/elpa package.
Since this file is created by package manager this is probably how it
adds Org to the load path, don't you think?
What I notice is that for elpa packages that don't hold such a line in their
Hi Rene,
Rene jl...@yahoo.com writes:
The way elpa works, it automatically adds packages to `load-path'. There is
therefore no need to have such a line
(add-to-list 'load-path (or (file-name-directory #$) (car load-path)))
in the `package-autoloads.el file.
Where is this file?
--
The way elpa works, it automatically adds packages to `load-path'. There is
therefore no need to have such a line
(add-to-list 'load-path (or (file-name-directory #$) (car load-path)))
in the `package-autoloads.el file.
Besides, having such a line leads to adding twice the same directory to
