From: Aaron Ecay <aaronecay@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] * lisp/ob-core.el (org-babel-execute-src-block): insert hash for silent results
Date: Tue, 12 Mar 2013 23:55:22 -0400 [thread overview]
Message-ID: <87ppz4ar85.fsf@gmail.com> (raw)
In-Reply-To: <87y5dwpbfi.fsf@gmail.com>
Hi Eric,
2013ko martxoak 9an, Eric Schulte-ek idatzi zuen:
> Could something like the following work? Removing ":results none" and
> adding something small as the returned result which may easily be parsed
> and placed in the buffer w/o problem.
>
> #+begin_src R :cache yes
> # code to perform side effect
> x <- 'side effect'
> 'done'
> #+end_src
>
> #+RESULTS[9f4e5b4b07e93c680ab37fc4ba1f75e1bfc0ee0a]:
> : done
It works, but it is a kludge. In fact, it is the same kludge that we
used to need before :results none (to avoid emacs choking on reading a
monster data frame).
> This does not need special built in support, e.g.,
>
> #+name: R-pid
> #+begin_src sh :var R="/usr/lib64/R/bin/exec/R"
> ps auxwww|grep "$R"|grep -v 'grep'|awk '{print $2}'
> #+end_src
>
> #+begin_src R :cache yes :var pid=R-pid
> # code to perform side effect
> x <- 'side effect'
> 'done'
> #+end_src
>
> #+RESULTS[da16f09882a6295815db51247592b77c80ed0056]:
> : done
Now *this* is a kludge! Since babel involves executing arbitrary code,
the question to ask is not “Is this possible in babel?”. The answer is
always “yes.” The right question is instead “What does it make the most
sense for babel to do?” I think Achim’s contributions to this thread
pushing us in the direction of thinking about what the execution model
is are exactly what is needed.
For cached code running in a session, I think a sensible model is:
- Code should be re-run once after each session startup
- Other than that, code should be re-run only if it changes, or if the
user explicitly requests it to be re-run.
In order to implement this, it is necessary to figure out how to hash
the contents of :results none blocks, and include the session process id
in the hash. If you have a different model in mind, then you will want
different behavior. But I think (thanks to Achim’s clarifying comments)
we can’t really discuss what is the “right” behavior without also
discussing which is the “right” model.
--
Aaron Ecay
next prev parent reply other threads:[~2013-03-13 3:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 4:07 [PATCH] * lisp/ob-core.el (org-babel-execute-src-block): insert hash for silent results Aaron Ecay
2013-03-08 21:25 ` Aaron Ecay
2013-03-08 22:07 ` Eric Schulte
2013-03-08 21:53 ` Achim Gratz
2013-03-08 22:09 ` Eric Schulte
2013-03-08 22:24 ` aaronecay
2013-03-09 17:45 ` Eric Schulte
2013-03-09 18:56 ` Aaron Ecay
2013-03-09 20:03 ` Achim Gratz
2013-03-09 0:57 ` Achim Gratz
2013-03-09 18:35 ` Eric Schulte
2013-03-09 19:22 ` Aaron Ecay
2013-03-09 20:26 ` Eric Schulte
2013-03-13 3:55 ` Aaron Ecay [this message]
2013-03-13 14:45 ` Eric Schulte
2013-03-19 4:49 ` Aaron Ecay
2013-03-23 22:34 ` Eric Schulte
2013-04-01 5:10 ` Aaron Ecay
2013-04-02 22:14 ` Eric Schulte
2013-03-10 8:52 ` Achim Gratz
2013-03-10 20:14 ` Sebastien Vauban
2013-03-10 21:06 ` Achim Gratz
2013-03-13 4:12 ` Aaron Ecay
2013-03-13 7:50 ` Achim Gratz
2013-03-13 14:42 ` Eric Schulte
2013-03-13 18:25 ` Achim Gratz
2013-03-14 19:52 ` Eric Schulte
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=87ppz4ar85.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/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).