emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Set or update timestamp after evaluation of code block?
Date: Mon, 21 Sep 2015 11:10:00 -0400	[thread overview]
Message-ID: <m2bncvrepj.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <m28u7zris1.fsf@krugs.de>

Here is one approach:

#+name: update-timestamp
#+BEGIN_SRC emacs-lisp :var data=""
(concat
 "Last run: "
 (format-time-string "[%Y-%m-%d %a %H:%M:%S]" (current-time))
 "\n" data)
#+END_SRC


#+BEGIN_SRC python :post update-timestamp(data=*this*)
print('hello')
#+END_SRC

#+RESULTS:
: Last run: [2015-09-21 Mon 11:09:18]
: hello



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?
>
> Thanks,
>
> Rainer

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

next prev parent reply	other threads:[~2015-09-21 15:10 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 [this message]
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
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=m2bncvrepj.fsf@andrew.cmu.edu \
    --to=jkitchin@andrew.cmu.edu \
    --cc=Rainer@krugs.de \
    --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

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).