From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Table formula from code block
Date: Tue, 24 Jan 2017 13:14:37 +0100 [thread overview]
Message-ID: <87ziig1wpe.fsf@luisa.c0t0d0s0.de> (raw)
In-Reply-To: <871svuf0dc.fsf@luisa.c0t0d0s0.de> (Michael Welle's message of "Mon, 23 Jan 2017 13:04:47 +0100")
Hello,
Michael Welle <mwe012008@gmx.net> writes:
...
> #+NAME: foo
> #+BEGIN_SRC emacs-lisp
>
> (+ 4 4)
> #+END_SRC
>
>
> | bar | foo |
> |--------+--------|
> | 42 | #ERROR |
>
> #+TBLFM: $2='(org-sbe "foo")::$1=42
>
> I'm not sure, what the problem is. Looking at org-sbe there is
> something, I don't understand. In the end org-babel-execute-src-block is
> called. That executes the _current_ source code block. But I don't
> understand, how foo (in this example) becomes the current source code
> block.
well, the docstring is a bit misleading, IMHO. Current source code block
means that the function looks around to find a source code block. I
though, it means the source code block 'I am in' at the moment.
I've tracked it down to org-babel-check-confirm-evaluate so far. In the
let*, export and eval are nil. The 5. element of info is nil, that means
(goto-char (nth 5 info)) will barf. Hmm.
Regards
hmw
next prev parent reply other threads:[~2017-01-24 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 12:27 Table formula from code block Roger Mason
2017-01-23 12:04 ` Michael Welle
2017-01-24 12:10 ` Roger Mason
2017-01-24 13:07 ` Michael Welle
2017-01-24 12:14 ` Michael Welle [this message]
[not found] ` <fbefc85e10fc401ebab2f7ef3794eade@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-24 9:04 ` Eric S Fraga
2017-01-24 10:52 ` Michael Welle
[not found] ` <a780781601084f15802822fade909e25@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-24 11:43 ` Eric S Fraga
2017-01-24 13:38 ` Michael Welle
2017-01-24 14:14 ` Michael Welle
[not found] ` <3b626627d0e74bd69bcf3a7941acf9f8@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-01-24 16:13 ` Eric S Fraga
2017-01-25 14:19 ` Michael Welle
2017-01-24 13:01 ` Michael Welle
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=87ziig1wpe.fsf@luisa.c0t0d0s0.de \
--to=mwe012008@gmx.net \
--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).