Closed tarsius closed 8 years ago
@tarsius Thanks!
"utilities.el" is a bad name for a library because any other package might come with a library by that name.
Indeed, now that this is pointed out... It's only for test though, not runtime.
Currently there are at least two packages that contain a utilities.el library: this and org-trello . I hope both of them get fixed.
Yes, they will.
Cheers,
It's only for test though, not runtime.
The problem is that utilities.el
was located in the same directory as org2jekyll.el
, so it was not possible to only put the directory containing the latter to the load-path
without that also making the former available at runtime.
Yes, they will.
Thanks!
The problem is that utilities.el was located in the same directory as org2jekyll.el
Ok, i forgot about this major detail. I thought i had it inside the test/ folder.
And indeed, some counter-examples where utilities.el is packaged for runtime:
For marmalade, it's ok https://github.com/ardumont/org2jekyll/blob/master/Cask#L6-L7.
So again, thanks for the heads up.
Cheers,
Thanks! This works for me now.
"utilities.el" is a bad name for a library because any other package might come with a library by that name.
Currently there are at least two packages that contain a
utilities.el
library: this and org-trello . I hope both of them get fixed.