Re: [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t

[John Kitchin <jkitchin@andrew.cmu.edu>]

I don't have a strong opinion on this. My sense is if you get a table it
is fine, if not, you should get a string. Most important to me is no
error. Of second importance is usability of the result.

If I add this after the block, it works as expected for me, so the
current behavior seems ok to me.

#+BEGIN_SRC emacs-lisp :var d=foo :results code
d
#+END_SRC

I am not actually sure if a string is usable, without a read statement
for emacs-lisp.

Nicolas Goaziou writes:

> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> Fabulous! Thanks!
>
> BTW,
>
>   #+BEGIN_SRC emacs-lisp
>     '((a (b)))
>   #+END_SRC
>
>   #+RESULTS: foo
>   | a | (b) |
>
> Shouldn't we also return lists deeper than 2 levels as strings? Does it
> even make sense to try formatting them into a table?
>
> Regards,

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu