From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: org tables into R?
Date: Wed, 07 Jan 2015 00:08:36 +0100 [thread overview]
Message-ID: <87d26ra4nf.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r3v8v8hx.fsf@gmail.com> (Aaron Ecay's message of "Mon, 05 Jan 2015 23:27:38 -0500")
Aaron Ecay <aaronecay@gmail.com> writes:
> You are correct about the silent dropping of macro-like text. However,
> with current master that case gives an undefined macro error, which is
> even worse.
I disagree. If we allow to insert macro-like text in the table, it will
become active in the generated table and will, sooner or later, generate
an undefined macro error anyway.
> Try this (in emacs -Q with org and ESS in the load-path) to
> see it:
>
> #+name: foo
> #+begin_src R
> c("foo","{{{bar}}}")
> #+end_src
Yes, an error is thrown, but
#+RESULTS: foo
| foo |
| {{{bar}}} |
is as cheesy. See above.
Macros are a very special kind of datum in Org. Luckily, their syntax is
awkward so you're unlikely to create one unwillingly. How common is your
example?
>> OTOH "ob-R.el" should consider using ":raw t" parameter for its table
>> conversion function.
>
> I think :raw is needed in ‘org-babel-insert-result’ in addition to my
> previous patch. New patch attached.
Actually, my advice doesn't stand. ":raw t" is not sufficient to prevent
macro expansion, which happens at the beginning of the export process.
Regards,
next prev parent reply other threads:[~2015-01-06 23:07 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 [this message]
2015-01-06 23:17 ` Aaron Ecay
2015-01-06 23:38 ` Nicolas Goaziou
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=87d26ra4nf.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).