From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: listing org source blocks in LaTeX
Date: Fri, 24 Sep 2010 16:00:54 +0200 [thread overview]
Message-ID: <87fwwzqm09.fsf@mundaneum.com> (raw)
In-Reply-To: F8263421-F644-4B20-AB35-70DA5228FD24@tsdye.com
Hi Thomas,
"Thomas S. Dye" wrote:
> Has anyone configured the listings package to recognize org source code
> blocks?
>
> On LaTeX export, I get this:
>
>> \lstset{language=org}
>>
>> org-buffer-color() $\equiv$
>> \begin{lstlisting}
>> #+LaTeX_CLASS_OPTIONS: [color]
>> \end{lstlisting}
>
> The listings package throws an error when it sees language=org.
Normal. It is unknown... unluckily!
> It does just fine with source code blocks in other languages.
I remember that Dan or Eric once told us to play with the following var:
--8<---------------cut here---------------start------------->8---
;; mapping between languages (listings in LaTeX) and their major mode
;; (in Emacs)
(setq org-src-lang-modes
'(("ocaml" . tuareg)
("elisp" . emacs-lisp)
;; ("Delphi" . perl)
("ditaa" . artist)
("asymptote" . asy)
("dot" . fundamental)))
--8<---------------cut here---------------end--------------->8---
Though, not sure it's set up in a right way. And, yes, this should be set up
properly in Org, I guess, instead of relying on the users to make this
customization?
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-09-24 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 21:26 listing org source blocks in LaTeX Thomas S. Dye
2010-09-24 14:00 ` Sébastien Vauban [this message]
2010-09-24 15:26 ` Eric Schulte
2010-09-24 19:00 ` Sébastien 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=87fwwzqm09.fsf@mundaneum.com \
--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).