From: myq <myqlarson@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Org Babel resolution of `:var` value reference inconsistent
Date: Sun, 01 Nov 2015 23:40:19 -0800 [thread overview]
Message-ID: <8737woetng.fsf@toshiba.i-did-not-set--mail-host-address--so-tickle-me> (raw)
Sometime since Org version 8.3beta and now, the way Org Babel resolves
the value of the `:var` header argument when assigned to a reference has
changed.
Previously, the following would work when exporting:
--8<---------------cut here---------------start------------->8---
* test
#+BEGIN_SRC R :var dat=table-data
print(summary(dat));
#+END_SRC
** COMMENT
#+TBLNAME: table-data
| number | measurement |
|--------+-------------|
| 1 | 10 |
--8<---------------cut here---------------end--------------->8---
The above /still/ works when manually evaluating the block (C-c C-c whil
in the block), but when exporting, the following error is thrown:
`org-babel-ref-resolve: Reference `table-data' not found in this buffer`
Curiously, the following tweak works for both manual evaluation and for
exporting and produces the same results that the above file used to
produce:
--8<---------------cut here---------------start------------->8---
#+OPTIONS: inline:nil
* test
#+BEGIN_SRC R :var dat=table-data
print(summary(dat));
#+END_SRC
*************** test
#+TBLNAME: table-data
| number | measurement |
|--------+-------------|
| 1 | 10 |
*************** END
--8<---------------cut here---------------end--------------->8---
This seems to be a bug, but perhaps there is a reason for this new
behaviour?
Thank you in advance for any insights.
next reply other threads:[~2015-11-02 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 7:40 myq [this message]
2015-11-02 9:01 ` Org Babel resolution of `:var` value reference inconsistent Andreas Leha
2015-11-02 13:19 ` Nick Dokos
2015-11-04 12:14 ` Andreas Leha
2015-11-05 12:56 ` Martin Carlé
2015-11-05 14:48 ` Nicolas Goaziou
2015-11-05 20:53 ` Andreas Leha
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=8737woetng.fsf@toshiba.i-did-not-set--mail-host-address--so-tickle-me \
--to=myqlarson@gmail.com \
--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).