From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: Set or update timestamp after evaluation of code block?
Date: Mon, 21 Sep 2015 11:37:32 -0400 [thread overview]
Message-ID: <87r3lrn5qb.fsf@yale.edu> (raw)
In-Reply-To: m28u7zris1.fsf@krugs.de
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.
next prev parent reply other threads:[~2015-09-21 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 12:46 Set or update timestamp after evaluation of code block? Rainer M Krug
2015-09-21 13:17 ` Eric S Fraga
2015-09-21 13:42 ` Rainer M Krug
2015-09-21 14:09 ` Eric S Fraga
2015-09-21 15:15 ` Rainer M Krug
2015-09-21 15:10 ` John Kitchin
2015-09-21 18:43 ` Rainer M Krug
2015-09-21 19:27 ` John Kitchin
2015-09-22 7:52 ` Rainer M Krug
2015-09-22 9:45 ` Rainer M Krug
2015-09-21 19:53 ` Grant Rettke
2015-09-22 7:56 ` PROPERTIES attached to results blocks - Was: " Rainer M Krug
2015-09-22 15:52 ` Charles C. Berry
2015-09-21 15:37 ` Jorge A. Alfaro-Murillo [this message]
2015-09-21 18:37 ` Rainer M Krug
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87r3lrn5qb.fsf@yale.edu \
--to=jorge.alfaro-murillo@yale.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
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).