From: "Eric Schulte" <schulte.eric@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: [babel] Bug in output PDF with source blocks of unknown language
Date: Mon, 18 Jan 2010 16:55:39 -0700 [thread overview]
Message-ID: <87iqazynlw.fsf@gmail.com> (raw)
In-Reply-To: <87iqb67z7g.fsf@gmail.com> (Eric Schulte's message of "Wed, 13 Jan 2010 09:21:23 -0700")
This should now be fixed.
"Eric Schulte" <schulte.eric@gmail.com> writes:
> Hi Sébastien,
>
> Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
>
> [...]
>
>> * Bug
>>
>> You see that when the language is unknown to Org-babel (=Delphi= in this
>> example), it gets ignored during export, and gets replaced by the previous
>> code block!!
>>
>> So, the current workaround is to take whatever other language know to Babel
>> (here: =perl=) for the export to (at least) output the right code in the
>> generated document (even if not correctly highlighted).
>>
>
> Oh, that certainly is a problem! Thanks for reporting I'll take a look.
> For reference it's being tracked as a bug on our development page here
>
> http://eschulte.github.com/babel-dev/TODO-on-export-babel-overwrites-unrecognized-source-blocks.html
>
>>
>> * Other problem
>>
>> The selected language must also be known by =listings=... Hence, =R= cannot
>> be chosen for language; generating otherwise an error when compiling the
>> LaTeX document.
>>
>
> This should be an easier fix. It is possible to add listings alias by
> adding an entry to the `org-src-lang-modes' variable.
>
> ,----[org-src-lang-modes]
> | org-src-lang-modes is a variable defined in `org-src.el'.
> | Its value is
> | (("ocaml" . tuareg)
> | ("elisp" . emacs-lisp)
> | ("ditaa" . artist)
> | ("asymptote" . asy)
> | ("dot" . fundamental))
> |
> |
> | Documentation:
> | Alist mapping languages to their major mode.
> | The key is the language name, the value is the string that should
> | be inserted as the name of the major mode. For many languages this is
> | simple, but for language where this is not the case, this variable
> | provides a way to simplify things on the user side.
> | For example, there is no ocaml-mode in Emacs, but the mode to use is
> | `tuareg-mode'.
> |
> | You can customize this variable.
> `----
>
> Best -- Eric
>
>>
>> Best regards,
>> Seb
>>
>> PS- I'll answer your posts shortly (Noweb vs Babel, and incompatibility with
>> Org-special-blocks). Have had no time up to now...
>
> I look forward to your reply when you do have time (no rush) -- notice
> I've made a slight change to the look of the source names when exported
> to LaTeX.
prev parent reply other threads:[~2010-01-18 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 16:04 [babel] Bug in output PDF with source blocks of unknown language Sébastien Vauban
2010-01-13 16:21 ` Eric Schulte
2010-01-18 23:55 ` Eric Schulte [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=87iqazynlw.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).