From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: =?UTF-8?B?UmU6IEJ1ZzogZXZhbHVhdGlvbiBvZiBhIGpzIGJsb2NrIHRoYXQg?= =?UTF-8?B?b3VwdXRzIGEgbGFyZ2UgYXJyYXkgZG9lcyBub3QgZm9ybWF0IHRoZSBvdXRw?= =?UTF-8?B?dXQgYXMgYSB0YWJsZSBbOC4yLjEwIChyZWxlYXNlXzguMi4xMCBAIGM6L0No?= =?UTF-8?B?b2NvbGF0ZXkvbGliL0VtYWNzLjI0LjQuMC4yMDE0MTEyMi90b29scy9zaGFy?= =?UTF-8?B?ZS9lbWFjcy8yNC40L2xpc3Avb3JnLyld?= Date: Sun, 28 Dec 2014 11:42:34 +0100 Message-ID: <877fxckqcl.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41878) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y5BIF-0001at-VZ for emacs-orgmode@gnu.org; Sun, 28 Dec 2014 05:41:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y5BIC-0006TL-PW for emacs-orgmode@gnu.org; Sun, 28 Dec 2014 05:41:51 -0500 Received: from relay5-d.mail.gandi.net ([2001:4b98:c:538::197]:41202) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y5BIC-0006Sr-Jo for emacs-orgmode@gnu.org; Sun, 28 Dec 2014 05:41:48 -0500 In-Reply-To: (Victor Valdivia's message of "Mon, 22 Dec 2014 02:03:22 -0300") 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: Victor Valdivia Cc: emacs-orgmode@gnu.org Hello, Victor Valdivia writes: > When I execute this snippet: > #+BEGIN_SRC js > return [[1, 2, 3, 4],[1, 2, 3, 4],[1, 2, 3, 4], [1, 2, 3, 4],[1, 2, 3, 4]]; > #+END_SRC > > I get this result instead of a table. > #+RESULTS: > : [[1 (\, 2) (\, 3) (\, 4)] (\, [1 (\, 2) (\, 3) (\, 4)]) (\, [1 (\, 2) (\, > 3) (\, 4)]) (\, [1 (\, 2) (\, 3) (\, 4)]) (\, [1 (\, 2) (\, 3) (\, 4)])] > > But when I generate a shorter table like this > #+BEGIN_SRC js > return [[1, 2, 3, 4],[1, 2, 3, 4],[1, 2, 3, 4], [1, 2, 3, 4]]; > #+END_SRC > > I get the expected result. > #+RESULTS: > | 1 | 2 | 3 | 4 | > | 1 | 2 | 3 | 4 | > | 1 | 2 | 3 | 4 | > | 1 | 2 | 3 | 4 | > > > I think that this happens when node.js generates a output with line > breaks, then the function org-babel-js-read cannot parse the output, but I > am not sure. I think this was fixed in development branch recently. Regards, -- Nicolas Goaziou