[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [PATCH] Process hlines in imported tables
From: |
Rick Frankel |
Subject: |
Re: [O] [PATCH] Process hlines in imported tables |
Date: |
Thu, 4 Apr 2013 14:30:36 -0400 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Apr 03, 2013 at 08:21:01PM +0200, 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.
I agree. "raw" results should probably be treated as scalar (with
cycling of the output to reformat an table :).
BTW, I am having problems wrapping my head around verbatim.
>From testing, it seems that verbatim acts the same as scalar.
rick
- Re: [O] [PATCH] Process hlines in imported tables, (continued)
Re: [O] [PATCH] Process hlines in imported tables, Rick Frankel, 2013/04/04
Re: [O] [PATCH] Process hlines in imported tables, Achim Gratz, 2013/04/04
Re: [O] [PATCH] Process hlines in imported tables,
Rick Frankel <=