emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Trouble with Tables and Python
Date: Tue, 15 Apr 2014 18:46:18 -0400	[thread overview]
Message-ID: <8738he9pol.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: CAHxk2pChMGqxvizmovd3gqHGZt3nRb5AKTQ_iHuN4r+Xg-HwDg@mail.gmail.com

Martin Schöön <martin.schoon@gmail.com> writes:

> ...  Let's move over to the third example file and the real
> mystery. This all my own code. Reading data from the first table works
> just fine and the same goes for the calculations. The output table,
> however, is different from that of example 2. The 'wrapper' is gone
> but each row is starting with ": ". Where does that come from? Why
> does it differ from example 2? If my results differ from someone
> else's (different install/versions etc) -- OK. But how can I get
> differences like this on my own? To my  un-trained eyes the print
> statements of examples 2 and 3 look very similar. (But, the first
> things that go blind are the eyes... probably something blatantly
> obvious once pointed out to me.)

2) and 3) are exactly the same thing (see section 11.3, "Literal
examples" in the org manual.)

The only difference is the length of the output - short output is
prepended by a colon, long output is wrapped in
#+BEGIN_EXAMPLE/#+END_EXAMPLE. What is short and what is long is
determined by the value of org-babel-min-lines-for-block-output
(default: 10) which you can customize.


  reply	other threads:[~2014-04-15 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 21:18 Trouble with Tables and Python Martin Schöön
2014-04-15 22:46 ` Nick Dokos [this message]
2014-04-16  1:29 ` John Kitchin
2014-04-16 18:58   ` Martin Schöön
2014-04-18 13:09   ` Sebastien Vauban

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:

  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=8738he9pol.fsf@alphaville.bos.redhat.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).