Re: ELPA

[Stefan Monnier]

>>> byte-compile=$(emacs) \
>>>   -batch \
>>>   -eval "(setq load-path (append load-path
>>> '(\"~/.emacs.d/elpa/gnuplot-mode-20171013.1616/\"
>>> \"~/.emacs.d/elpa/vterm-20201004.2057\"
>>> \"~/.emacs.d/elpa/markdown-mode-20201015.1327\"
>>> \"~/.emacs.d/elpa/w3m-20200818.141\" \"~/.emacs.d/emacs-init\"
>>> \"~/.emacs.d/emacs-init/ide\" \"~/.emacs.d/emacs-init/w3m\"
>>> \"~/.emacs.d/emacs-init/gnus\"
>>> \"~/.emacs.d/elpa/google-translate-20190620.1416\" )))" \
>>>   -f batch-byte-compile
>>>
>>> In the Makefile? (Set the load-path again for every pack, I mean.)
>>
>> Which Makefile?
>
> https://dataswamp.org/~incal/emacs-init/Makefile
>
>> I think the answer is something like:
>>
>>     byte-compile=$(emacs)                      \
>>        --batch --eval "(package-activate-all)" \
>>        -f batch-byte-compile
>
> 80 errors of this, the same kind:

I didn't mean for you to use this literally.  Obviously, you'll need to
adapt it to your specific circumstance.  The `package-activate-all`
should take care of all the ~/.emacs.d/elpa/*


        Stefan