emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Tutorial for Beamer export seems to lack settings
Date: Sat, 06 Aug 2011 20:58:11 +0200	[thread overview]
Message-ID: <807h6qiczg.fsf@somewhere.org> (raw)
In-Reply-To: CAGzSEhf1v-zAyA=cwz4sSK38ZnKsZ830FGD+-fpxYg9njaj7VA@mail.gmail.com

Hi LanX,

LanX wrote:
> seems like I found the solution, see

I'm glad.

> * Org Export Latex Listings:
> ...
>    If you want to use this, you also need to make LaTeX use the
>    listings package, and if you want to have color, the color
>    package.  Just add these to `org-export-latex-packages-alist',
>    for example using customize, or with something like
>
>      (require 'org-latex)
>      (add-to-list 'org-export-latex-packages-alist '("" "listings"))
>      (add-to-list 'org-export-latex-packages-alist '("" "color"))
>
> maybe this should be mentioned in the tutorial.
>
> Actually I don't understand why this flag doesn't automatically include the
> latex-package listings.

What do you mean by flag?  Those packages?  Yes, on one side, I agree it'd be
better if they'd been included by default. Though, some people use other
packages to provide support for coloring code in LaTeX, namely minted.
Hence... no default choice, to allow everybody to choose what he prefers.

> Nevermind the other problem with BEAMER_FRAME_LEVEL, it was a consequence of
> trying to solve the former one.

Excellent!

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2011-08-06 18:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06 14:25 Tutorial for Beamer export seems to lack settings LanX
2011-08-06 15:07 ` Sebastien Vauban
2011-08-06 15:31   ` LanX
2011-08-06 16:52     ` LanX
2011-08-06 18:58       ` Sebastien Vauban [this message]
2011-08-06 18:55     ` 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:
  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=807h6qiczg.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.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).