Hi Bastien, thanks for you reply, in particular for showing how to avoid org-insert-time-stamp to convert the current-time into a string.
I should have said more clearly what I had in mind with this. I was thinking of a reproducible report or manuscript with R source blocks that produce some results. Here org babel allows one to enable caching for some or all source-blocks. My proposal has two advantages: 1) when visiting the cached results of a particular block after some time, e.g. one year later, it would be visible *when* the block was evaluated. This can be useful, e.g., when there are several versions of the same dataset which are used to produce the cached results. 2) sometimes it may be unclear which blocks are evaluated when running org-babel-execute-buffer or org-export-as-x, in particular for org-babel novices. Thus, showing the evaluation time in the results header will help to learn how caching works. Cheers Thomas Bastien <b...@altern.org> writes: > Hi Thomas, > > Thomas Alexander Gerds <t...@biostat.ku.dk> writes: > >> (when hash (concat "[["hash"][" (with-temp-buffer >> (org-insert-time-stamp (current-time) 'hm)) "]]")) >> but, not sure if that is a good idea and what other changes this >> would require. > > I'm not sure too (both whether this is a good idea and whether this > would trigger other changes)... but I'd say this is a very specific > need, and it can be fulfilled by asking the code to insert a timestamp > into the exported results, right? > > See for e.g.: > #+BEGIN_SRC emacs-lisp :results raw > (message ";; %s" (format-time-string (cdr org-time-stamp-custom-formats))) > #+END_SRC > HTH, --
