From: Richard Stanton <stanton@haas.berkeley.edu>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Problems exporting LaTeX source code
Date: Tue, 19 Mar 2013 17:13:40 +0000 [thread overview]
Message-ID: <CD6DEA60.14027%stanton@haas.berkeley.edu> (raw)
In-Reply-To: <m18v5jmicr.fsf@tsdye.com>
Thanks for the suggestion, Thomas.
I changed "source" to "code" and tried again. The results were exactly the
same as with "source".
Best,
Richard Stanton
On 3/19/13 10:04 AM, "Thomas S. Dye" <tsd@tsdye.com> wrote:
>Richard Stanton <stanton@haas.berkeley.edu> writes:
>
>> Using org mode version 8.0-pre (release_8.0-pre-91-g437c62), I'm having
>> trouble exporting LaTeX lists (itemize, description). Here's a sample
>>file:
>>
>> #+title: Sample org file
>> * Section 1
>> Some LaTeX source:
>> #+begin_src latex :exports source
>> \begin{itemize}
>> \item Item 1
>> \item Item 2
>> \end{itemize}
>> #+end_src
>>
>>
>>
>> 1) When I export this to HTML, I get a box showing "\begin{itemize}" but
>> the rest of the box is blank.
>>
>> 2) When I export to LaTeX/PDF, I get something like (this is cut and
>> pasted from the PDF file):
>>
>> Some LATEX source:
>> [frame=lines,fontsize=,linenos]latex
>> € Item 1
>> € Item 2
>>
>>
>> In other words, it looks like the LaTeX source is actually being
>>compiled,
>> and some internal org-mode exporter options look like they're being
>> exported to the PDF file.
>>
>> Am I doing something wrong here?
>
>Perhaps. I don't see =source= on the list of :exports header arguments.
>If you change =source= to =code= does it work?
>
>hth,
>Tom
>
>--
>Thomas S. Dye
>http://www.tsdye.com
prev parent reply other threads:[~2013-03-19 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 16:37 Problems exporting LaTeX source code Richard Stanton
2013-03-19 17:04 ` Thomas S. Dye
2013-03-19 17:13 ` Richard Stanton [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CD6DEA60.14027%stanton@haas.berkeley.edu \
--to=stanton@haas.berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.