[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [BUG][babel] ":result output table" doesn't work for python code
From: |
Eric S Fraga |
Subject: |
Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks |
Date: |
Wed, 27 Apr 2011 11:09:27 +0100 |
User-agent: |
Gnus/5.110016 (No Gnus v0.16) Emacs/24.0.50 (gnu/linux) |
"Eric Schulte" <address@hidden> writes:
[...]
>
> Hi Eric,
>
> Does the matlab/octave `disp' function display tabular data in the same
> manner as it is written literally in source code?
Hi Eric!
No, unfortunately not. Arrays (tabular data) are written out using only
whitespace for formatting:
--8<---------------cut here---------------start------------->8---
*** simple example
#+srcname: octave-simple
#+begin_src octave :results output
A = [1, 2; 3, 4];
disp(A)
#+end_src
#+results: octave-simple
: 1 2
: 3 4
--8<---------------cut here---------------end--------------->8---
> This is part of the issue with the "output table" :results combination,
> namely what constitutes a table for printed output. In source code the
> answer is obvious, namely whatever the language's interpreter would read
> as a literal table, however with printed output there are many possible
> ways to represent tabular data, but none *is* tabular in the way that
> source code can *be* tabular.
Yes, that makes sense.
> If the printed output is exactly the same as how a table would be
> written in matlab/octave source code, then does my patched version work?
> If not, then rather than writing another table parser, perhaps the data
> could be printed as an Org-mode table, and then the "output raw"
> :results combination could be used, or the output could be sent through
> another code block to convert the string to a table.
That's what I do at the moment, actually.
Mind you, org is able to take the output and convert it to a table
easily enough with =C-c |= (org-table-create-or-convert-from-region)
operating on the output if selected as a region. Would it be possible
to post-process the output from babel automatically using this method
(maybe with a hook?) with the output selected if ":results output
table", say, were specified? That alone would be sufficient for 90% of
the cases...
Apologies for the sporadic nature of my responses lately: I have been on
holiday (much needed!) and purposely without email most of the time!
Thanks,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.209.g1a687)
- [O] [BUG][babel] ":result output table" doesn't work for python code blocks, Ethan Ligon, 2011/04/14
- Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks, Eric Schulte, 2011/04/14
- Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks, Eric S Fraga, 2011/04/15
- Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks, Eric Schulte, 2011/04/15
- Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks, Eric S Fraga, 2011/04/22
- Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks, Eric Schulte, 2011/04/26
- Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks,
Eric S Fraga <=
- Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks, Eric Schulte, 2011/04/27
- Re: [O] [BUG][babel] ":result output table" doesn't work for python code blocks, Eric S Fraga, 2011/04/27