From: Nicolas Goaziou <firstname.lastname@example.org>
To: Severin Kempf <email@example.com>
Subject: Re: macro with inline source does not work in table cells
Date: Thu, 12 Apr 2018 20:40:13 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Severin Kempf's message of "Thu, 12 Apr 2018 14:32:44 -0400")
Severin Kempf <firstname.lastname@example.org> writes:
> This is very cumbersome for my particular document, which has a large
> number of cells that I am working with. I could add an additional column
> to facilitate this, but I don't see a good way to hide that column from
> the exporter -- I only want the result, not the data needed to generate
> the result.
You can pass header arguments to the `org-sbe' call. It may be possible
to get the results without the data.
> What is preventing it from working in the table cell? What is
> allowing a simpler macro expansion to work inside of a table cell?
The parser. Inline Babel code is not parsed in table cells. This could
conflict with TBLFM lines.
next prev parent reply other threads:[~2018-04-12 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 18:09 macro with inline source does not work in table cells kabriel
2018-04-11 10:52 ` Nicolas Goaziou
2018-04-12 18:32 ` Severin Kempf
2018-04-12 18:40 ` Nicolas Goaziou [this message]
2018-04-12 21:02 ` Severin Kempf
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 \
* 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).