From: Aaron Ecay <aaronecay@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org, tsd@tsdye.com
Subject: Re: Best practices for literate programming [was: Latex export of tables]
Date: Thu, 18 Apr 2013 13:59:28 -0400 [thread overview]
Message-ID: <87r4i7ra7z.fsf@gmail.com> (raw)
In-Reply-To: <877gjzsrtt.fsf@pank.eu>
Hi Rasmus,
2013ko apirilak 18an, Rasmus-ek idatzi zuen:
> I too rely heavily on filters and customizations. I haven't been able
> to fully appreciate the asynchronous exporter yet.
>
> For instance I set some defaults for tables, pictures, add lots of
> entities etc. in my init file, and I went as far as writing a separate
> init file just loading just the org stuff. Now, this is clearly /not/
> a very reproducible way of doing this.
>
> So I'm really interested in hearing or seeing implementation where the
> goal is reproducibility. On one hand I can appreciate keeping Org
> close to a vanilla state. On the other hand, I'd have to overwrite
> defaults every time (e.g. I /always/ want booktab tables). I guess I
> could keep an emacs-lisp block in the top of the file specifying
> stuff, but it also seems kind of tedious (copy-pasting every time).
> (Perhaps this could be resolved by loading external files hosted
> somewhere accessible).
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).
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.
--
Aaron Ecay
next prev parent reply other threads:[~2013-04-18 17:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 8:06 Latex export of tables Vikas Rawal
2013-04-14 23:29 ` Suvayu Ali
2013-04-16 11:56 ` Vikas Rawal
2013-04-16 13:13 ` Thomas Alexander Gerds
2013-04-16 17:39 ` Suvayu Ali
2013-04-16 20:07 ` Thomas S. Dye
2013-04-16 21:39 ` Suvayu Ali
2013-04-16 23:45 ` Thomas S. Dye
2013-04-17 10:21 ` Myles English
2013-04-16 22:10 ` Best practices for literate programming [was: Latex export of tables] Vikas Rawal
2013-04-17 0:06 ` Thomas S. Dye
2013-04-18 16:53 ` Rasmus
2013-04-18 17:59 ` Aaron Ecay [this message]
2013-04-18 18:25 ` Rasmus
2013-04-18 19:48 ` Achim Gratz
2013-04-18 19:42 ` Thomas S. Dye
2013-04-21 17:25 ` Rasmus Pank Roulund
2013-04-17 6:39 ` Suvayu Ali
2013-04-17 9:55 ` Rainer M. Krug
2013-04-17 10:10 ` Suvayu Ali
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r4i7ra7z.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
--cc=tsd@tsdye.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).