From: Maurizio Vitale <email@example.com>
To: Dan Davison <firstname.lastname@example.org>
Subject: Re: org-babel feature request
Date: Sun, 11 Oct 2009 10:05:56 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Dan Davison's message of "Sun, 11 Oct 2009 00:32:02 -0400")
>>>>> "Dan" == Dan Davison <email@example.com> writes:
Dan> Maurizio Vitale <firstname.lastname@example.org>
>>>>>>> "Dan" == Dan Davison <email@example.com> writes:
Dan> Maurizio Vitale
>> >> 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.
Dan> The other, perhaps nicer, thing you can do is change the
Dan> #+srcname of the block which has the effect of changing the
Dan> results block. You can do that now. But maybe we could allow
Dan> the user to over-ride the default way in which the #+resname
Dan> tag is set? E.g. by adding a :resname header argument.
Dan> Something like this:
Dan> #+srcname: test2 #+begin_src sh :resname test2-redirected expr
Dan> 2 + 3 #+end_src
Dan> #+resname: test2 : 4
Dan> #+resname: test2-redirected : 5
Dan> Do you think that would be worthwhile?
Too early for me to say. First reaction is that I don't see particular
advantages in the :resname method over the changing the src name to
justify the additional implementation effort.
What I think would be useful is a way to switch all results/srcnames in
a file by adding a prefix/suffix. So:
would cause results to go to #+resname: test if
org-mode-babel-source-prefix is nil, but would go to
#+resname: example-test if
org-mode-babel-source-prefix is "example-"
and then org-mode-babel-source-prefix could be set somewhere in the
Maybe the #+resname which is updated could be marked with a '*' so that
if somebody does C-c C-c and doesn't see an update he's reminded that
the result block is not active because of a prefix.
Thanks for the suggestion of changing the source block name: it goes a
long way towards what I need.
>> 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,
prev parent reply other threads:[~2009-10-11 14:03 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
2009-10-11 14:05 ` Maurizio Vitale [this message]
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 \
* 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).