all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org
Subject: Best practices for literate programming [was: Latex export of tables]
Date: Wed, 17 Apr 2013 03:40:22 +0530	[thread overview]
Message-ID: <20130416221022.GA7809@panahar> (raw)
In-Reply-To: <m1bo9e9r41.fsf@poto.westell.com>



> > I'm suggesting this because if you continue on this path, i.e. litter
> > your Org file with hacks, soon you will end up with an extremely fragile
> > and complicated Org project.  I have been down that road while writing
> > my thesis.  

I see the point. I think there is a need for documenting different
approaches people have used so far to avoid this. I suggest we use
this thread to start a discussion. If we get useful content, it should
perhaps land up somewhere on worg eventually.

> At one point I realised the problem and made the decision to
> > split things into two kinds of files: static content (document
> > structuring, text, plots, etc), and dynamic content (babel, TikZ blocks
> > that generate tables, plots, figures, etc used by the static content
> > files).  It is still reproducible research, but modular and less hacky
> > (hence more stable).

Suvayu,

This is indeed a very neat approach. Would you kindly elaborate?

Would it be too much work for you to get some illustrations from your
work?

In your scheme of things, how do you finally combine the static and
the dynamic content?

Any chance that you could release the source of something like a
chapter of your thesis for people to see? Or may be create something
with dummy content?

> I've been down it too many times myself. The habits I've developed
> over time have helped, but I think they are less systematic than
> what you've devised.

Tom, do tell us more about what these habits are.

>  I'd love to see some notes on your solution as
> a brief tutorial or an expanded FAQ on Worg. 

+1

> I'll be happy to
> contribute or help if you find time to do something like this.

and +1.

Vikas

  parent reply	other threads:[~2013-04-16 22:10 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         ` Vikas Rawal [this message]
2013-04-17  0:06           ` Best practices for literate programming [was: Latex export of tables] Thomas S. Dye
2013-04-18 16:53             ` Rasmus
2013-04-18 17:59               ` Aaron Ecay
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130416221022.GA7809@panahar \
    --to=vikaslists@agrarianresearch.org \
    --cc=emacs-orgmode@gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.