From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG][babel] ":result output table" doesn't work for python code blocks
Date: Wed, 27 Apr 2011 11:09:27 +0100 [thread overview]
Message-ID: <87aafc9fag.fsf@pinto.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <87zkncolm9.fsf@gmail.com> (Eric Schulte's message of "Tue, 26 Apr 2011 13:31:26 -0600")
"Eric Schulte" <schulte.eric@gmail.com> 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)
next prev parent reply other threads:[~2011-04-27 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 0:46 [BUG][babel] ":result output table" doesn't work for python code blocks Ethan Ligon
2011-04-15 2:26 ` Eric Schulte
2011-04-15 10:35 ` Eric S Fraga
2011-04-15 16:13 ` Eric Schulte
2011-04-20 20:28 ` Eric S Fraga
2011-04-26 19:31 ` Eric Schulte
2011-04-27 10:09 ` Eric S Fraga [this message]
2011-04-27 13:16 ` Eric Schulte
2011-04-27 15:28 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aafc9fag.fsf@pinto.chemeng.ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).