From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [PATCH] Process hlines in imported tables Date: Thu, 04 Apr 2013 15:59:36 +0200 Message-ID: <867gkiz99z.fsf@somewhere.org> References: <20130329014615.GA49671@BigDog.local> <87wqsq6yd1.fsf@gmail.com> <20130329214238.GA53401@BigDog.local> <87r4ixah7y.fsf@gmail.com> <20130330234151.GA53721@BigDog.local> <87mwtkqtzh.fsf@gmail.com> <20130331122900.GA57939@BigDog.local> <87vc83bhma.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Achim, Achim Gratz wrote: > Rick Frankel writes: >> Missed verbatim. Thanks for the pointer, it works, but i think that >> perl is double-processing returned values. If we do the same things in >> elisp i get (my) expected results: >> >> #+begin_src elisp :results raw >> "|c1|c2| >> |- >> |a|1| >> |b|2|"; >> #+end_src > > Elisp is different from all other languages: it doesn't do any > processing of strings to begin with for value returns. The reason that > Perl processes "raw" results is that org-babel-result-cond does not > switch to the "scalar" path for this condition, which is why you need > the extra "verbatim". It probably should, though, so if Eric agrees > then I will push a change that does this. IIUC, wouldn't that be changing the default answer to "how to interpret the results" just for Perl? While the default answer for all languages seems to be "table"? Best regards, Seb -- Sebastien Vauban