emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: "Christopher W. Ryan" <cryan@binghamton.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: still struggling with workflow
Date: Thu, 06 Sep 2012 15:43:24 -0400	[thread overview]
Message-ID: <4614.1346960604@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from "Christopher W. Ryan" <cryan@binghamton.edu> of "Thu, 06 Sep 2012 14:48:00 EDT." <5048EFE0.4080702@binghamton.edu>

Christopher W. Ryan <cryan@binghamton.edu> wrote:

> I've been using org-mode for, oh about a year now, and it seems like a
> very useful tool. But I'm still struggling to understand and implement
> effective workflows for projects, re-using bits and pieces of text.
> For example, I have a general project related to heat wave morbidity and
> mortality, and indoor heat index. Hopefully I can parlay it into a
> number of distinct studies, each with IRB applications, grant
> applications, and papers (all pdf output), and presentations (beamer pdf
> output.)  For example, all my stuff for the first study is in a single
> org file, HeatWaves1.org. The second project's documents will need to
> re-use much of that material, but not all of it; and there will be some
> new material.
> Is it viable to keep everything related to my heat wave work, for all
> substudies, in the one org file, and customize the output to my needs at
> different times, via judicious use of headlines and :export tags?  Or is
> it best to start a new org file for each substudy and copy/paste what is
> needed from the old?

I should think you can do it either way: only you can decide what the
best way is. If you decide to go the second way, you might want to
investigate the #+INCLUDE mechanism: maybe you can use it to reduce

I'm not an org "power user", so take the following with the
appropriately-sized grain (or boulder) of salt: I would start with a
single file and try to organize it in a way that encourages reuse, and
be able to do what you need to do today and possibly tomorrow; don't
worry too much about the day after tomorrow. If/when you find that the
process is broken, or the processing takes too long, then reorganize it,
massively if necessary; splitting it into multiple files might be the
more natural thing to do at that point, but with the experience you have
gained, you will probably be able to do that more reliably than when

Obviously, this is my personal biased view, and others might disagree.

Bernt Hansen's write-up (http://doc.norang.ca/org-mode.html), as well as
some of Tom Dye's project write-ups (check the "Reproducible Research
Examples" section of
http://orgmode.org/worg/org-contrib/babel/uses.html) might be good
bedtime reading material: it's unlikely that they will answer your
specific questions, but they might inspire you to come up with better
solutions to your problems.


  reply	other threads:[~2012-09-06 19:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 18:48 still struggling with workflow Christopher W. Ryan
2012-09-06 19:43 ` Nick Dokos [this message]
2012-09-06 23:07   ` Jambunathan K

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:

  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=4614.1346960604@alphaville.americas.hpqcorp.net \
    --to=nicholas.dokos@hp.com \
    --cc=cryan@binghamton.edu \
    --cc=emacs-orgmode@gnu.org \


* 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


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).