Re: Set or update timestamp after evaluation of code block?

[jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)]

Rainer M Krug writes:

> Eric S Fraga <e.fraga@ucl.ac.uk> writes: 
> 
>> On Monday, 21 Sep 2015 at 14:46, Rainer M Krug wrote: 
>> 
>> [...] 
>> 
>>> Is it possible to set a timestamp (ur update it when it exists 
>>> already) when a code block has been evaluated, so that I have 
>>> e record when it was updated? 
>> 
>> Could you make use of the :post header argument to invoke emacs 
>> lisp and execute org-time-stamp-inactive in some way? 
> 
> Thanks - sounds possible? But if I just use 
> 
> ,---- | :post (org-time-stamp-inactive) `---- 
> 
> 1) an input is required and 2) the time stamp is inserted before 
> the #+begin_src and makes the block invalid. 
> 
> How can I put the time stamp in the line after the #+end_src or 
> possibly even in the same line, as this does not seem to have an 
> impact on the source block?

You could use the :epilogue header argument. Since you want after 
the #+end_src this is rather hackish:

:epilogue (save-excursion (re-search-forward "END_SRC" nil nil 2) 
(org-insert-time-stamp (current-time) t t "\nEvaluated: " "\n"))

It does not update the results, but it will show you all the 
results and when they were evaluated.

If you want to keep only one set of results and do not mind having 
the timestamp before the #+BEGIN_SRC, you could use something 
like:

:epilogue (save-excursion (if (re-search-backward "Last evaluated: 
" nil t) (kill-line 1)) (org-insert-time-stamp (current-time) t t 
"Last evaluated: " "\n"))

Best,
-- 
Jorge.