From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: org tables into R?
Date: Wed, 07 Jan 2015 00:38:44 +0100 [thread overview]
Message-ID: <878uhfa397.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87fvbnv6qk.fsf@gmail.com> (Aaron Ecay's message of "Tue, 06 Jan 2015 18:17:55 -0500")
Aaron Ecay <aaronecay@gmail.com> writes:
> Nothing unwilling about it – I had been deliberately trying to generate a
> table with macros in it as the result of a babel block. These macros are
> defined in the document, in order to encapsulate some fiddly typesetting
> which recurs very commonly.
>
> Shouldn’t this workflow be supported?
Note that Babel blocks are evaluated after macro expansion. As
a consequence, the workflow above is hardly useful, as it requires its
user to manually evaluate all blocks generating macros /before/
exporting the document.
If the workflow is not used and doesn't have intrinsic value, I don't
think we need to invent kludges to support it.
> In any case, the point is broader: the orgtbl-* functions cannot cope
> with macros in their input at all (not just in the context of babel). I
> think the programmatic interface to org tables ought to be composable
> with macros.
orgtbl-* are not an API for tables, but converters.
My point is still valid: you don't have a real use-case, so just don't
bother.
Regards,
next prev parent reply other threads:[~2015-01-06 23:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 19:57 org tables into R? Michael Gauland
2015-01-02 20:13 ` Andreas Leha
2015-01-02 22:45 ` Vikas Rawal
2015-01-04 10:01 ` Andreas Leha
2015-01-05 0:10 ` Aaron Ecay
2015-01-05 11:48 ` Nicolas Goaziou
2015-01-06 4:27 ` Aaron Ecay
2015-01-06 23:08 ` Nicolas Goaziou
2015-01-06 23:17 ` Aaron Ecay
2015-01-06 23:38 ` Nicolas Goaziou [this message]
2015-01-06 10:14 ` Andreas Leha
2015-01-06 11:02 ` Rainer M Krug
2015-01-06 12:07 ` Andreas Leha
2015-01-06 13:37 ` Rainer M Krug
2015-01-06 17:49 ` Aaron Ecay
2015-01-07 9:01 ` Rainer M Krug
2015-01-04 3:19 ` Michael Gauland
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=878uhfa397.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).