From: "Sean O'Halpin" <sean.ohalpin@gmail.com>
To: dmg@uvic.ca
Cc: emacs-orgmode@gnu.org
Subject: Re: babel :results output and format of output
Date: Sun, 24 Feb 2013 11:51:43 +0000 [thread overview]
Message-ID: <CAOXM+eUi9kicdHL2DPrKtjyHbho8H0-u71YikjJk1FTTUR7yvA@mail.gmail.com> (raw)
In-Reply-To: <87ip5iyoii.fsf@mn.cs.uvic.ca>
On Sun, Feb 24, 2013 at 10:50 AM, D M German <dmg@uvic.ca> wrote:
>
> hi everybody,
>
>
> I have been testing babel with perl and I am very puzzled by the
> following:
>
>
> Say I have the following script that outputs 10 numbers. org/babel wraps
> it as a begin_example
>
>
> #+begin_src perl :results output
> for (my $i=0;$i<10;$i++) {
> print "$i\n";
> }
> #+end_src
>
> #+RESULTS:
> #+begin_example
> 0
> 1
> 2
> 3
> 4
> 5
> 6
> 7
> 8
> 9
> #+end_example
>
>
> But if my script only outputs 9 lines then the format is not wrapped by
> #+begin_example, and instead is prefixed by :
>
> #+begin_src perl :results output
> for (my $i=0;$i<9;$i++) {
> print "$i\n";
> }
> #+end_src
>
> #+RESULTS:
> : 0
> : 1
> : 2
> : 3
> : 4
> : 5
> : 6
> : 7
> : 8
>
> Is this behaviour expected? Is the threshold at which it happens
> configurable?
Yes - it's controlled by =org-babel-min-lines-for-block-output= in
lisp/ob-core.el:
#+BEGIN_QUOTE
(defvar org-babel-min-lines-for-block-output 10
"The minimum number of lines for block output.
If number of lines of output is equal to or exceeds this
value, the output is placed in a #+begin_example...#+end_example
block. Otherwise the output is marked as literal by inserting
colons at the starts of the lines. This variable only takes
effect if the :results output option is in effect.")
#+END_QUOTE
Regards,
Sean
prev parent reply other threads:[~2013-02-24 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 10:50 babel :results output and format of output D M German
2013-02-24 11:51 ` Sean O'Halpin [this message]
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=CAOXM+eUi9kicdHL2DPrKtjyHbho8H0-u71YikjJk1FTTUR7yvA@mail.gmail.com \
--to=sean.ohalpin@gmail.com \
--cc=dmg@uvic.ca \
--cc=emacs-orgmode@gnu.org \
/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).