From: Ista Zahn <izahn@psych.rochester.edu>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: cleaning all the #+results from an org document
Date: Thu, 28 Jul 2011 12:15:53 -0400 [thread overview]
Message-ID: <CA+vqiLFvfwQ1QUy3XfiK5bMQs8R+RN4XvVPvci4MF4VtyXHfAA@mail.gmail.com> (raw)
In-Reply-To: <32216.1311857987@maps>
On Thu, Jul 28, 2011 at 8:59 AM, Stephen Eglen
<S.J.Eglen@damtp.cam.ac.uk> wrote:
> Thanks Torsten, you've expressed it elegantly!
>>
>> a) send it to someone without the results (to let him create his own)
>> b) archive them without having possible huge amount of lines of
>> results which can be reproduced any time by executing the block again.
>> c) to delete all the old results and start "fresh"
+1 for c. I often work with R objects that are simply too large to
store in org tables, so I use babel caching + session + write / load R
data files from disk. This works, but it becomes easy to get to an
inconsistent state, and I would like to be able to delete the results
blocks and run the whole thing fresh.
Best,
Ista
>
> I was mostly thinking about b (for putting into version control) and c,
> for giving to students to try out.
>
> Stephen
>
>
--
Ista Zahn
Graduate student
University of Rochester
Department of Clinical and Social Psychology
http://yourpsyche.org
next prev parent reply other threads:[~2011-07-28 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 8:31 cleaning all the #+results from an org document Stephen Eglen
2011-07-28 9:21 ` suvayu ali
2011-07-28 11:41 ` Stephen Eglen
2011-07-28 11:58 ` suvayu ali
2011-07-28 11:41 ` Sebastien Vauban
2011-07-28 12:24 ` Torsten Wagner
2011-07-28 12:59 ` Stephen Eglen
2011-07-28 16:15 ` Ista Zahn [this message]
2011-07-28 23:04 ` Eric Schulte
2011-07-29 7:48 ` Sebastien Vauban
2011-07-29 8:15 ` Sebastien Vauban
2011-07-29 16:38 ` Eric Schulte
2011-07-29 14:42 ` Torsten Wagner
2011-07-29 16:40 ` Eric Schulte
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=CA+vqiLFvfwQ1QUy3XfiK5bMQs8R+RN4XvVPvci4MF4VtyXHfAA@mail.gmail.com \
--to=izahn@psych.rochester.edu \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).