From: Puneeth <punchagan@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: export to latex broken
Date: Fri, 20 Aug 2010 22:45:11 +0530 [thread overview]
Message-ID: <AANLkTikaVykE=aj3pM35LELViakJkoEQ1KNjHi8gzHMx@mail.gmail.com> (raw)
In-Reply-To: <E3D34790-2AB4-4482-B35C-1E39E0E8030E@gmail.com>
On Fri, Aug 20, 2010 at 9:55 PM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
>
> On Aug 20, 2010, at 4:36 PM, Puneeth wrote:
>
>> Hi,
>>
>> Exporting from org to LaTeX is broken on the master.
>>
>> Git bisect gives the bad commit as 034dbac3eecd
>> "Search for LaTeX setup case-insensitively"
>
> OK, I have reverted it.
>
> Can you please describe what happened?
Sorry for the incomplete report. I'd been using C-c C-e ?d and getting
a direct pdf output which was garbled.
Getting a LaTeX output and compiling gives me a clearer picture.
The documentclass is getting appended with a "random" character.
pdflatex gave me this error
-------------------------------------------
! Undefined control sequence.
l.2 \documentclassT
{article}
-------------------------------------------
Removing that "T" from the end of documentclass solves the problem.
(and I think the T is coming from the org file itself. I get a
different character in different documents.)
HTH,
Puneeth
next prev parent reply other threads:[~2010-08-20 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 14:36 export to latex broken Puneeth
2010-08-20 16:24 ` Eric S Fraga
2010-08-20 16:25 ` Carsten Dominik
2010-08-20 17:15 ` Puneeth [this message]
2010-08-20 17:15 ` Nick Dokos
2010-08-20 17:26 ` Eric S Fraga
-- strict thread matches above, loose matches on Subject: below --
2011-03-01 10:50 suvayu ali
2011-03-01 11:24 ` Nicolas
2011-03-01 11:35 ` Suvayu Ali
2011-03-01 11:42 ` Nicolas
2011-03-01 11:59 ` Suvayu Ali
2011-03-01 11:49 ` Suvayu Ali
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='AANLkTikaVykE=aj3pM35LELViakJkoEQ1KNjHi8gzHMx@mail.gmail.com' \
--to=punchagan@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.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).