emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Daniele Pizzolli <dan@toel.it>, emacs-orgmode@gnu.org
Subject: Re: [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t
Date: Tue, 24 Feb 2015 13:21:41 -0500	[thread overview]
Message-ID: <m2y4nndvbe.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <8761ar45kp.fsf@nicolasgoaziou.fr>

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

next prev parent reply	other threads:[~2015-02-24 18:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 12:48 [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t Daniele Pizzolli
2015-02-23 12:57 ` John Kitchin
2015-02-23 13:17   ` Daniele Pizzolli
2015-02-23 15:43     ` John Kitchin
2015-02-23 17:46       ` Nicolas Goaziou
2015-02-23 18:07         ` John Kitchin
2015-02-24 16:50           ` Nicolas Goaziou
2015-02-24 18:21             ` John Kitchin [this message]
2015-02-24 23:36             ` [PATCH] was " Charles C. Berry
2015-02-25 13:44               ` Nicolas Goaziou
2015-02-23 19:30         ` Daniele Pizzolli

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=m2y4nndvbe.fsf@andrew.cmu.edu \
    --to=jkitchin@andrew.cmu.edu \
    --cc=dan@toel.it \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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

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).