Aaron Ecay <aarone...@gmail.com> writes: > If your external org configuration file were kept under version control > (I’ll discuss git but the principle is general), then reproducibility > would be possible. There are ways of embedding git hashes in LaTeX > documents (for one example: > http://thorehusfeldt.net/2011/05/13/including-git-revision-identifiers-in-latex/), > and of course org could help automate this. Including the git hash of > the document itself, the config file, and org-mode’s own code (assuming > these are kept in 3 separate repos) should allow perfect reproducibility > (modulo incompatible changes in emacs, I guess).
Sounds interesting. I'll check it out. > It would be interesting for org to have an ability to reference files > not just by name, but by git revision. So that you could do something > like (where 123456 is some git hash): > #+include: [[gitbare:/path/to/repo::123456:my-org-setup-file.org]] > and have org take care of checking out the proper revision and loading > the file in the usual way. This syntax is already implemented, for > plain links, in contrib/lisp/org-git-link.el, so it is just a matter > of making #+include and friends understand links in addition to > filenames. Now that is a great idea that allows for both incremental improvements while still retaining compatibility for old files. –Rasmus -- And let me remind you also that moderation in the pursuit of justice is no virtue
