emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: Maurizio Vitale <maurizio.vitale@polymath-solutions.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-babel feature request
Date: Sun, 11 Oct 2009 00:32:02 -0400	[thread overview]
Message-ID: <87r5ta1rgd.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <87y6niws4r.fsf@polymath-solutions.com> (Maurizio Vitale's message of "Sat, 10 Oct 2009 23:01:40 -0400")

Maurizio Vitale <maurizio.vitale@polymath-solutions.com> writes:

>>>>>> "Dan" == Dan Davison <davison@stats.ox.ac.uk> writes:
>     Dan> Maurizio Vitale
>     Dan> <mav@cuma.i-did-not-set--mail-host-address--so-tickle-me>
>     Dan> writes:
>     Dan> [...]
>     >> It would be nice if it was possible to have multiple result
>     >> sections. This way I could embed in the document the result that
>     >> was obtained when writing the documentation, while still allowing
>     >> the person following the recipe to evaluate again the shell
>     >> script and get the results on his machine.
>     >> 
>     >> The first section should be read-only (not necessarily physically
>     >> read-only, but skipped by C-c C-c). The others may be
>     >> re-evaluated over and over until the end user has a valid
>     >> configuration.
>     Dan> Hi Maurizio,
>     Dan> Once I've obtained the results that I want to "freeze", I would
>     Dan> manually alter (or even delete) the #+resname tag, so that the
>     Dan> source block no longer overwrites it. Is that simple solution
>     Dan> appropriate? I'm not yet seeing the advantage of the more
>     Dan> complex possibilities.
> That is the obvious possibility, but at times you may want to
> re-evaluate those: either the configuration has changed, or the software
> you're documenting has changed or the script you're using is buggy.
> Yes you could reintroduce the #+resname tag when needed, but I'm hoping
> to get more automation than M-x shell-command-on-region.

The other, perhaps nicer, thing you can do is change the #+srcname of
the block which has the effect of changing the results block. You can do
that now. But maybe we could allow the user to over-ride the default way
in which the #+resname tag is set? E.g. by adding a :resname header

Something like this:

--8<---------------cut here---------------start------------->8---
#+srcname: test2
#+begin_src sh :resname test2-redirected
  expr 2 + 3

#+resname: test2
: 4

#+resname: test2-redirected
: 5
--8<---------------cut here---------------end--------------->8---

Do you think that would be worthwhile?


> I've just started using org-babel in this way, so I'm not sure at all of
> what features I'll feel in the end needed. This seems one right now.
> Best regards,
>      Maurizio

  reply	other threads:[~2009-10-11  4:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11  1:23 org-babel feature request Maurizio Vitale
2009-10-11  2:45 ` Dan Davison
2009-10-11  3:01   ` Maurizio Vitale
2009-10-11  4:32     ` Dan Davison [this message]
2009-10-11 14:05       ` Maurizio Vitale

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=87r5ta1rgd.fsf@stats.ox.ac.uk \
    --to=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=maurizio.vitale@polymath-solutions.com \


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