From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: table not returned Date: Tue, 03 Apr 2012 08:21:53 +0200 Message-ID: <874nt1qqri.fsf@gnu.org> References: <87ty19ak2b.fsf@med.uni-goettingen.de> <87pqbx4wn7.fsf@gnu.org> <87zkb1c5jx.fsf@med.uni-goettingen.de> <16747.1332938738@alphaville> <87r4wcdfga.fsf@med.uni-goettingen.de> <17334.1332944459@alphaville> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55101) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SEx6f-00053b-JZ for emacs-orgmode@gnu.org; Tue, 03 Apr 2012 02:20:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SEx6d-0001Zn-VW for emacs-orgmode@gnu.org; Tue, 03 Apr 2012 02:20:41 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:38152) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SEx6d-0001ZS-Mm for emacs-orgmode@gnu.org; Tue, 03 Apr 2012 02:20:39 -0400 Received: by werj55 with SMTP id j55so2805501wer.0 for ; Mon, 02 Apr 2012 23:20:37 -0700 (PDT) In-Reply-To: <17334.1332944459@alphaville> (Nick Dokos's message of "Wed, 28 Mar 2012 10:20:59 -0400") 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: nicholas.dokos@hp.com Cc: Andreas Leha , emacs-orgmode@gnu.org, schulte eric Hi Nick, Nick Dokos writes: > BTW, two possible workarounds which "work" with org-babel-string-read: > > (org-babel-string-read "[foo]") --> [foo] > > (org-babel-string-read "'(bar)") --> (bar) > > do *not* work in the original context, so the org-babel-string-read > problem is probably only part of the story. Try this: (org-babel-read "(bar)") => error (org-babel-read "(bar)" t) => ok What is at stake here is that perhaps `org-babel-read' should be more clever in turning `inhibit-lisp-eval' automatically on in some contexts. But Eric has the last word on this, I'm not familiar enough with the code. Thanks, -- Bastien