From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniele Pizzolli Subject: Re: [BUG] babel eval of emacs-lisp: orgtbl-to-orgtbl: Wrong type argument: listp, t Date: Mon, 23 Feb 2015 14:17:12 +0100 Message-ID: <867fv8sr6v.fsf@me.localhost.invalid> References: <86lhjossj6.fsf@me.localhost.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45579) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YPstV-0003bV-JO for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 08:17:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YPstO-0005aM-W6 for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 08:17:53 -0500 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:42402) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YPstO-0005a9-Pt for emacs-orgmode@gnu.org; Mon, 23 Feb 2015 08:17:46 -0500 In-Reply-To: (John Kitchin's message of "Mon, 23 Feb 2015 07:57:44 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: John Kitchin Cc: emacs-orgmode@gnu.org John Kitchin writes: > I am pretty sure this is a long-standing "feature". > > Try this: > #+BEGIN_SRC emacs-lisp :results raw > (org-babel-do-load-languages > 'org-babel-load-languages > '((emacs-lisp . nil) > (R . t))) > #+END_SRC > > I have never been able to use a babel block that outputs a list of cons > cells without explicitly setting results to raw or code. The problem > here is your code evaluates to ((emacs-lisp) (R . t)), and the t somehow > gets interpreted like it should be a list, which it is not. So, it > cannot be made into a table for output, and you get your error. > > Changing the header just bypasses this function and outputs the results > more directly. Hello John, 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. Best, Daniele