Bastien <b...@gnu.org> writes: > Rainer M Krug <rai...@krugs.de> writes: > >> So the reason why I think it would be advantageous to have these files >> in org does not lie with the programmer familiar with emacs-lisp, but >> with somebody familiar with the other side. > > Sorry I was too terse in my previous answer: I completely agree with > the goal you describe, but I don't think adding an .org source along > the .el output (say e.g. ob-R.org and ob-R.el) will simplify my life > as a maintainer: each time an ob-*.org file is changed we need to > tangle it again... and this leads to auto-tangling, auto-committing > considerations that I don't even want to start thinking about.
I absolutely see your point, and I agree that doing this manually is out of the question. But I am wondering if it would be possible to automate this process, i.e. using git post server side hooks? I must admit that I don't have any experience with this, but it sounds about the thing one could use to automatically tangle the file. But as I am not the one who has to maintain it, it is easy for me to suggest it. Cheers, Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D): +49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982
pgpUYhIDn2ngN.pgp
Description: PGP signature
