From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: 'listings' package used but not required in LaTeX export
Date: Sun, 09 Jun 2013 09:34:48 +0200 [thread overview]
Message-ID: <87bo7fwxd3.fsf@gmail.com> (raw)
In-Reply-To: <871u8cqhxa.fsf@gmail.com> (Thorsten Jolitz's message of "Sun, 09 Jun 2013 01:52:33 +0200")
Hello,
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> Thorsten Jolitz <tjolitz@gmail.com> writes:
>>
>>> but there is no
>>>
>>> ,----------------------
>>> | \usepackage{listings}
>>> `----------------------
>>
>> This is a feature to my understanding.
>
> mmhh ... I would rather say that the defaults can be as simple as
> possible (or desired), but should result in reasonable output without
> any user interaction. But without adding a \usepackage{listings} or
> modifying the variables you mention the LaTeX output is unusable in this
> case.
>
>> Several packagess can format, and I for instance prefer pygments if I
>> need code formatting.
>
> Then the default should be loading one of them rather than using package
> macros in the exported LaTeX sources without loading a package that
> contains those macros.
>
>> You could add listings to your packages list, either
>> org-latex-packages-alist or even org-latex-default-packages-alist, if
>> you really want to.
>>
>> You could probably also write a clever filter to load a package if it
>> is missing.
>
> I could, and thanks for the tips, but I still think this can be
> considered a bug (if I'm not the only one having the problem).
By default, `org-latex-listings' is nil, which means no "listings" code
is inserted in the output. Therefore, the problem comes from your
configuration (i.e. you changed variable's value without reading its
docstring).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-06-09 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 19:41 'listings' package used but not required in LaTeX export Thorsten Jolitz
2013-06-08 23:16 ` Rasmus
2013-06-08 23:52 ` Thorsten Jolitz
2013-06-09 7:34 ` Nicolas Goaziou [this message]
2013-06-09 11:50 ` Thorsten Jolitz
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=87bo7fwxd3.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@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).