Re: [PATCH] Process hlines in imported tables

[Achim Gratz <Stromeko@nexgo.de>]

Sebastien Vauban writes:
> Achim Gratz wrote:
>> 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"?

Again, org-babel-result-cond doesn't interpret "raw" at all at the
moment, which I think is a bug.  This leads to the interpretation of
multiline strings and strings with separators in the return value as
tables.  Not all Babel languages are using that macro, so these
implementations might have a different interpretation (which may or may
not be a bug in itself).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds