* feature request: re-compute cache without evaluation
@ 2012-04-12 8:49 Henning Redestig
2012-04-12 12:12 ` Eric Schulte
0 siblings, 1 reply; 3+ messages in thread
From: Henning Redestig @ 2012-04-12 8:49 UTC (permalink / raw)
To: emacs-orgmode
Hi,
I write many source blocks that take a fairly long time to execute
(several minutes). Sometimes I find myself wanting to do cosmetic
changes to the code, that I know (for sure) do not change the output,
after the first evaluation. Unfortunately, after having made these
changes the cache obviously does not match the code anymore and I have
to re-evaluate to update the cache. I know it goes against the strict
'reproducible research' idea but still I would like to be able to
re-compute the cache without actually evaluating the block as it is
not efficient to re-evaluate for the sole purpose of updating the
cache.
What do you think?
--
/Henning
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: feature request: re-compute cache without evaluation
2012-04-12 8:49 feature request: re-compute cache without evaluation Henning Redestig
@ 2012-04-12 12:12 ` Eric Schulte
2012-04-12 14:50 ` Henning Redestig
0 siblings, 1 reply; 3+ messages in thread
From: Eric Schulte @ 2012-04-12 12:12 UTC (permalink / raw)
To: Henning Redestig; +Cc: emacs-orgmode
Henning Redestig <henning.red@googlemail.com> writes:
> Hi,
>
> I write many source blocks that take a fairly long time to execute
> (several minutes). Sometimes I find myself wanting to do cosmetic
> changes to the code, that I know (for sure) do not change the output,
> after the first evaluation. Unfortunately, after having made these
> changes the cache obviously does not match the code anymore and I have
> to re-evaluate to update the cache. I know it goes against the strict
> 'reproducible research' idea but still I would like to be able to
> re-compute the cache without actually evaluating the block as it is
> not efficient to re-evaluate for the sole purpose of updating the
> cache.
>
> What do you think?
Press C-c C-v a (org-babel-sha1-hash) in the code block, then manually
replace the original hash with the hash returned by that function.
--
Eric Schulte
http://cs.unm.edu/~eschulte/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: feature request: re-compute cache without evaluation
2012-04-12 12:12 ` Eric Schulte
@ 2012-04-12 14:50 ` Henning Redestig
0 siblings, 0 replies; 3+ messages in thread
From: Henning Redestig @ 2012-04-12 14:50 UTC (permalink / raw)
To: Eric Schulte; +Cc: emacs-orgmode
ah, this was easy, thanks!
2012/4/12 Eric Schulte <eric.schulte@gmx.com>:
> Henning Redestig <henning.red@googlemail.com> writes:
>
>> Hi,
>>
>> I write many source blocks that take a fairly long time to execute
>> (several minutes). Sometimes I find myself wanting to do cosmetic
>> changes to the code, that I know (for sure) do not change the output,
>> after the first evaluation. Unfortunately, after having made these
>> changes the cache obviously does not match the code anymore and I have
>> to re-evaluate to update the cache. I know it goes against the strict
>> 'reproducible research' idea but still I would like to be able to
>> re-compute the cache without actually evaluating the block as it is
>> not efficient to re-evaluate for the sole purpose of updating the
>> cache.
>>
>> What do you think?
>
> Press C-c C-v a (org-babel-sha1-hash) in the code block, then manually
> replace the original hash with the hash returned by that function.
>
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte/
--
/Henning
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-04-12 14:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-12 8:49 feature request: re-compute cache without evaluation Henning Redestig
2012-04-12 12:12 ` Eric Schulte
2012-04-12 14:50 ` Henning Redestig
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).