From: Ista Zahn <istazahn@gmail.com>
To: Malcolm Purvis <malcolm@purvis.id.au>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Tangling and Exporting an Unsupported Language.
Date: Wed, 1 Oct 2014 10:22:40 -0400 [thread overview]
Message-ID: <CA+vqiLFXDKiFuq+kd9++RmCNBp-WOQg03DuuCqS+4StMzOD-6w@mail.gmail.com> (raw)
In-Reply-To: <m2ppecxo2n.fsf@purvis.id.au>
On Wed, Oct 1, 2014 at 3:10 AM, Malcolm Purvis <malcolm@purvis.id.au> wrote:
>>>>>> "Ista" == Ista Zahn <istazahn@gmail.com> writes:
>
> Ista> Exporting and tangling don't require any language support.
>
> Ista> #+begin_src foobarbas :tangle foo.bar
> Ista> +end_src
>
> Ista> is perfectly fine and will export and tangle just fine. Or did I
> Ista> misunderstand your question?
>
> Thanks, I wasn't aware that you could put an arbitrary string as the
> language.
>
> I also found that I had org-latex-listings set to t, which was making
> LaTeX error because it didn't know about the languages I was trying.
>
> I've now switched the using the minted LaTeX package, which supports
> 'text' as a language, and have started using that.
Yes, I find minted much nicer that listings, the only drawback being
that it has external dependencies. I guess you've already discovered
that you can do
(add-to-list 'org-export-latex-minted-langs '(foo "bar"))
where foo is the name of the language and bar is the pygments lexer
that should be used to typeset it.
Best,
Ista
>
> Thanks for your help.
>
> Malcolm
>
> --
> Malcolm Purvis <malcolm@purvis.id.au>
>
prev parent reply other threads:[~2014-10-01 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 6:53 Tangling and Exporting an Unsupported Language Malcolm Purvis
2014-09-29 19:22 ` Ista Zahn
2014-10-01 7:10 ` Malcolm Purvis
2014-10-01 14:22 ` Ista Zahn [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=CA+vqiLFXDKiFuq+kd9++RmCNBp-WOQg03DuuCqS+4StMzOD-6w@mail.gmail.com \
--to=istazahn@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=malcolm@purvis.id.au \
/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).