Hi Rene,
Rene writes:
> Achim Gratz 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
Achim Gratz 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
`package-autol
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?
Bastien 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?
Hi Rene,
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?
--
Bastien
