From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Best practices for literate programming [was: Latex export of tables] Date: Thu, 18 Apr 2013 20:25:27 +0200 Message-ID: <87ppxrr90o.fsf@pank.eu> References: <20130412080600.GA18235@panahar> <20130414232953.GC11696@kuru.dyndns-at-home.com> <20130416115619.GA12405@panahar> <20130416173948.GC7402@kuru.dyndns-at-home.com> <20130416221022.GA7809@panahar> <877gjzsrtt.fsf@pank.eu> <87r4i7ra7z.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34961) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UStdN-0001nI-Q5 for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 14:32:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UStXL-0001Hm-90 for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 14:26:42 -0400 Received: from plane.gmane.org ([80.91.229.3]:45448) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UStXK-0001He-Ve for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 14:26:23 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UStXE-0005ic-IQ for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 20:26:16 +0200 Received: from dynamic-adsl-94-34-137-181.clienti.tiscali.it ([94.34.137.181]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Apr 2013 20:26:16 +0200 Received: from rasmus by dynamic-adsl-94-34-137-181.clienti.tiscali.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 18 Apr 2013 20:26:16 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Aaron Ecay 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