Jambunathan K <kjambunat...@gmail.com> writes: > If we reconcile what happens here with what is done in Makefile, may be > we can uncover why certain macros in org-macs.el doesn't propagated to > some set of files.
If byte-compile-directory is available in all versions of Emacs, then I could certainly use it in the Makefile. Not sure if I can get to it before the weekend, but I will try it out soon-ish. > Note that org-macs.el issue is increasingly reported only with emacs-23 > and not with emacs-24. One of the reason could be that emacs-24 > *already* has most of the macro definitions in the system path. This is > not the case with emacs-23 installations which have (much?) older > versions of org. I may be missing what the "org-macs.el issue" is, precisely. > From what I understand package manager compiles files in alphabetical > order. It means that org-macs.el gets compiled after org-agenda.el. With make (at least after "make clean") it's exactly the same thing. What I don't understand is if package manager uses the already customized load-path or the bog-standard one, like make does via "emacs -Q". > Also when eval-when-compile is done of org-macs.el - somewhere it should > be done right? - I don't know which of the org-macs.el gets loaded. Is > it system-installed one or the one in the distribution tar. That would depend on which one it finds first, hence the question of what load-path looks like at that point. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
