From: Dan Davison <davison@stats.ox.ac.uk>
To: "Sébastien Vauban"
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: [BUG] latex export of verbatim environments
Date: Thu, 07 Oct 2010 16:00:07 +0100 [thread overview]
Message-ID: <87aamqnj48.fsf_-_@stats.ox.ac.uk> (raw)
In-Reply-To: <8739sidt1v.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Thu, 07 Oct 2010 15:35:40 +0200")
>>> #+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).
>>>
> 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,
>
> OK... In a way, you confirm my point of view, considering that both are
> equivalent in Org...
>
>
>> then perhaps it is a bug that they have non-equivalent latex export?
>
> Exactly what I'm thinking...
>
>
>> I didn't realise that begin_example resulted in a lstlisting environment
>> when using listings with Org.
>
> My only custom (AFAIK) is:
>
> ;; tell org to use listings (instead of verbatim) for source code
> (setq org-export-latex-listings t)
>
> ;; if you want fontified source code, then you must include the
> ;; `listings' package
> (add-to-list 'org-export-latex-packages-alist '("" "listings") t)
>
> ;; if you want colored source code, then you need to include the
> ;; `xcolor' package
> (add-to-list 'org-export-latex-packages-alist '("" "xcolor") t)
>
>
>>> 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.
>
> I find it nice (not to say necessary) to have a space after the colon in the
> Org buffer.
>
> But, when exporting, as both have been added as a prefix in front of every
> result line, both should be removed, ensuring no extra space in the LaTeX
> output...
OK, I think the conclusion of this that
1. It does not reveal a bug in babel.
2. There may be a bug in the listings export code in that it fails to
recognise colons as a verbatim environment
3. There may be a second bug in the vanilla latex export code in that it
should remove the space which follows the protective colon.
Dan
>
> Thanks for your answer.
>
> Best regards,
> Seb
prev parent reply other threads:[~2010-10-07 15:01 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
2010-10-07 13:35 ` Sébastien Vauban
2010-10-07 14:37 ` Dan Davison
2010-10-07 15:00 ` Dan Davison [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=87aamqnj48.fsf_-_@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.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).