emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Minshall <minshall@umich.edu>
To: "Berry, Charles" <ccberry@health.ucsd.edu>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: using previous =#+results= when =:eval never=
Date: Sun, 04 Jul 2021 08:19:23 +0300	[thread overview]
Message-ID: <3981138.1625375963@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Sat, 03 Jul 2021 19:08:09 +0000." <AFFDC856-200D-4ABE-99DE-266EBD4A571B@health.ucsd.edu>


thanks.  (i'm not surprised at an e-lisp suggestion from you! :)

i worry about accidental modification of the base case results during
the chaos of development.  it occurs to me (reading through
(org-babel-ref-resolve)) to keep my base case source blocks marked with
[:results silent], which should prevent accidental modification. (*)

then, i would change [:results silent] to, e.g., [:results silentx], in
the base case source blocks whenever i wanted to re-create those

for, e.g., inspecting the results when things differ, it would be nice
to stay in the language of the rest of the code.  but i suspect i'll be
able to do some e-lisp magic on the RHS of a :var, e.g., crudely

: #+begin_src R :var basecaseresults=(org-babel-read-named-result "testcountsdecompose")

i'll play around with it.  (i suspect i'll be motivated to use an e-lisp
macro, to eliminate the quotes, for example.)

again, thanks.

cheers, Greg

(*) this relies on current org-mode behavior, where
(org-babel-read-result) will return results from a result block from a
source block marked [:results silent].  i have no idea how likely this
behavior is to change in the long run.

  reply	other threads:[~2021-07-04  5:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 16:35 using previous =#+results= when =:eval never= Greg Minshall
2021-07-03 19:08 ` Berry, Charles via General discussions about Org-mode.
2021-07-04  5:19   ` Greg Minshall [this message]
2021-07-04 17:20     ` Berry, Charles via General discussions about Org-mode.

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:

  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=3981138.1625375963@apollo2.minshall.org \
    --to=minshall@umich.edu \
    --cc=ccberry@health.ucsd.edu \
    --cc=emacs-orgmode@gnu.org \


* 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


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