From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type
 argument: listp, t
Date: Mon, 23 Feb 2015 10:43:38 -0500
Message-ID: <m2a904iqfp.fsf@andrew.cmu.edu>
References: <86lhjossj6.fsf@me.localhost.invalid>
	<m2bnkk9453.fsf@andrew.cmu.edu>
	<867fv8sr6v.fsf@me.localhost.invalid>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44478)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jkitchin@andrew.cmu.edu>) id 1YPvAt-0000QD-QH
	for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 10:44:00 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jkitchin@andrew.cmu.edu>) id 1YPvAq-0003A4-K3
	for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 10:43:59 -0500
Received: from smtp.andrew.cmu.edu ([128.2.157.38]:48647)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jkitchin@andrew.cmu.edu>) id 1YPvAq-00039z-Ez
	for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 10:43:56 -0500
In-reply-to: <867fv8sr6v.fsf@me.localhost.invalid>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Daniele Pizzolli <dan@toel.it>
Cc: emacs-orgmode@gnu.org

>
> thanks for the explanation.
>
> Unfortunately my lisp knowledge is too limited to understand you.  As a
> naive org-mode user, if possible I do not want to be exposed to org
> internals error, especially the confusing ones, where the custom code
> works fine.  Maybe we can get a warning instead of an error?
>
> It is not a really big issue, a newcomer can be confused, if not scared,
> having an error on the fist babel usage.

I agree. Even for experienced people, this is pretty annoying. Something
as simple as


#+BEGIN_SRC emacs-lisp
'((1 . nil) (2 . 3))
#+END_SRC

fails with a cryptic error. While this works fine. I would vote for a
fall-back to code or even a plain string in this case.

#+BEGIN_SRC emacs-lisp :results code
'((1 . nil) (2 . 3))
#+END_SRC

#+RESULTS:
#+BEGIN_SRC emacs-lisp
((1)
 (2 . 3))
#+END_SRC



>
> Best,
> Daniele

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