From: Dan Davison <davison@stats.ox.ac.uk>
To: "Sébastien Vauban"
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@lo.gmane.org>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [Org-Babel] Export environments for shell results?
Date: Wed, 06 Oct 2010 16:26:04 +0100 [thread overview]
Message-ID: <87y6abwdf7.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <87y6abicqw.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Wed, 06 Oct 2010 17:04:23 +0200")
Hi Seb,
Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
writes:
> #+TITLE: Org-Babel export environments for shell results
>
> * Example
>
> ** Medium output
>
> #+srcname: is-converted-to-listings
> #+begin_src sh :results output :exports both
> grep autoload ~/Downloads/emacs/site-lisp/org-mode/lisp/ob.el | cut -d "#" -f 4
> #+end_src
(It's nice that your email is in Org format; I can get the contents into
an Org buffer quickly. Could I ask you to make the source blocks
reproducible in the future, so that we can execute them without having
to alter file paths etc?)
>
> #+results: is-converted-to-listings
> #+begin_example
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> #+end_example
>
> gets translated (in LaTeX) to:
>
> #+begin_src latex
> \begin{lstlisting}
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> autoload
> \end{lstlisting}
> #+end_src
>
> ** Short output
>
> ... while
>
> #+srcname: is-converted-to-verbatim
> #+begin_src sh :results output :exports both
> grep autoload ~/Downloads/emacs/site-lisp/org-mode/lisp/ob.el | cut -d "#" -f 4 | head -n 3
> #+end_src
>
> #+results: is-converted-to-verbatim
> : autoload
> : autoload
> : autoload
>
> gets translated (in LaTeX) to:
>
> #+begin_src latex
> \begin{verbatim}
> autoload
> autoload
> autoload
> \end{verbatim}
> #+end_src
>
> with a leading space (that you don't see when running the command in the
> shell).
>
> The only difference is the shell command is adding =head -n 3=.
>
> * Questions
>
> 1. Why that difference of behavior?
I suspect this is due to
--8<---------------cut here---------------start------------->8---
org-babel-min-lines-for-block-output is a variable defined in `ob.el'.
Its value is 10
Documentation:
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.
--8<---------------cut here---------------end--------------->8---
>
> 2. What's the determining factor for switching between =verbatim= and
> =lstlisting= environments?
I'm no expert on latex export. But if the colon form and the block form
are equivalent in Org, then perhaps it is a bug that they have
non-equivalent latex export? I didn't realise that begin_example
resulted in a lstlisting environment when using listings with Org.
>
> 3. Why is there a leading space in the =verbatim= environment?
I guess it is due to the space after the colon in the Org buffer.
Dan
>
> Best regards,
> Seb
next prev parent reply other threads:[~2010-10-06 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 15:04 [Org-Babel] Export environments for shell results? Sébastien Vauban
2010-10-06 15:26 ` Dan Davison [this message]
2010-10-07 13:35 ` Sébastien Vauban
2010-10-07 14:37 ` Dan Davison
2010-10-07 15:00 ` [BUG] latex export of verbatim environments Dan Davison
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=87y6abwdf7.fsf@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@lo.gmane.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).