From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: latex code block evaluation -- Eric?
Date: Mon, 11 Feb 2013 16:37:37 +0100 [thread overview]
Message-ID: <86d2w697zy.fsf_-_@somewhere.org> (raw)
In-Reply-To: 87liavf7p8.fsf@bye.fritz.box
Hi Henry,
henry atting wrote:
> "Sebastien Vauban" writes:
>> henry atting wrote:
>>> I have this latex code block:
>>>
>>> #+begin_src latex :file foo.pdf
>>> \documentclass{article}
>>> \begin{document}
>>> ...some text...
>>> \end{document}
>>> #+end_src
>>>
>>> After evaluation the resulting file looks like this:
>>>
>>> article ...some text...
>>>
>>> I do not understand this. As far as I know it is possible to define the
>>> latex documentclass within a code block.
>>
>> Could you be more explicit? Do you want to use that to pass parameters to the
>> LaTeX backend? If yes, why not using the "#+LaTeX:" directive (not sure
>> they're still supported with the exact same syntax as before -- I've not yet
>> merged my documents). And that brings us to the most important question: old
>> or new exporter?
>>
>> Eventually, can you send a real ECM, or your real use case?
>
> Ah, I see, I was unclear.
> In this case I simply want to evalutate this code block with `C-c C-c'.
> I do not use the orgmode LaTeX exporter, only the HTML exporter.
> Finally I will create org files with LaTeX code blocks which I will export to
> HTML. And that's all. HTML export works fine with the old or the new
> exporter.
>
> Though in this case it is not really indispensable I only was wondering why
> code block evalution does not work as expected. Why is
> `\documentclass{article}' not recognized properly?
To be sure to understand, what are you expecting when you're evaluating the
LaTeX code block? Its content to be automagically converted to a PDF file
thru the LaTeX chain?
AFAIK, this does not work. I'd like it to be the case, but Eric Schulte once
explained it was (too?) difficult. Dunno if it's still on his task list.
The workaround was to tangle to a TeX file, and from there to compile to a PDF
via AUCTeX. Yes, not sexy, I know.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-02-11 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 18:17 latex code block evaluation henry atting
2013-02-10 21:10 ` Sebastien Vauban
2013-02-11 10:47 ` henry atting
2013-02-11 15:37 ` Sebastien Vauban [this message]
2013-02-11 16:19 ` Eric Schulte
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=86d2w697zy.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).