From: Matthew Lundin <mdl@imapmail.org>
To: "Holst Thomas (DS-ET/ECF1)" <Thomas.Holst@de.bosch.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug in LaTeX export
Date: Fri, 10 Jul 2009 07:45:20 -0500 [thread overview]
Message-ID: <m2y6qw1zbz.fsf@fastmail.fm> (raw)
In-Reply-To: <23C69956B336A746BD3E1CD955C7A6992A51205019@SI-MBX03.de.bosch.com> (Holst Thomas's message of "Fri\, 10 Jul 2009 12\:50\:06 +0200")
"Holst Thomas (DS-ET/ECF1)" <Thomas.Holst@de.bosch.com> writes:
> I think I discoverd a bug in LaTeX export. I mark a subtree with C-c @
> and then export it to LaTeX with C-c C-e L.
>
> If the subtree has no further subtrees the LaTeX-file not only contains
> the region, but also the rest of the document to the end.
>
> Here is an example:
>
> ,----[ test.org ]
> | * Kapitel 1
> | ** Kapitel 1.1
> | foo bar
> | * Kapitel 2
> | bar foo
> `----
>
> If the Kapitel 1.1 subtree is marked the LaTeX output looks like this:
>
> ,----[ LaTeX output ]
> | % Created 2009-07-10 Fr 12:33
> | \documentclass[11pt,a4paper]{article}
> | \usepackage[latin1]{inputenc}
> | \usepackage[T1]{fontenc}
> | \usepackage{hyperref}
> |
> |
> | \title{Kapitel 1.1}
> | \author{Holst Thomas}
> | \date{10 Juli 2009}
> |
> | \begin{document}
> |
> | \textbf{Kapitel 1.1}
> |
> | \setcounter{tocdepth}{3}
> | \tableofcontents
> | \vspace*{1cm}
> | foo bar
> | \begin{itemize}
> | \item Kapitel 2
> | bar foo
> | \end{itemize}
> |
> | \end{document}
> `----
>
> Kapitel 2 is also included. This does not happen if the subtree has
> additonal subtrees. If I mark the Kapitel 1 subtree the output is as
> expected.
>
> When the bug happens, `org-export-latex-default-class' does not work.
> Instead the class 'article' is used.
>
> It does not happen if the region is exported to ASCII or HTML.
>
> My setup is:
>
> emacs 22.2.1, WinXP, org-mode 6.28trans from yesterday.
Do you have transient-mark-mode enabled? I tested this with Emacs 22 and
when transient-mark-mode was enabled, it exported correctly (i.e., just
the 1st tree). When transient-mark-mode was turned off, I got the
results you describe above.
Just a thought...
Best,
Matt
next prev parent reply other threads:[~2009-07-10 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 10:50 Bug in LaTeX export Holst Thomas (DS-ET/ECF1)
2009-07-10 12:19 ` Matthew Lundin
2009-07-10 12:45 ` Matthew Lundin [this message]
2009-07-10 12:56 ` AW: " Holst Thomas (DS-ET/ECF1)
2009-07-10 14:36 ` Matthew Lundin
2009-07-16 19:43 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2011-11-28 14:57 Bug in latex export Markus Grebenstein
2011-11-12 11:13 Markus Grebenstein
[not found] <nneething-c:/daten/users/DE_hts2fe/Mail/org-answers/001.txt@FE-Z1102>
2009-07-17 10:46 ` Bug in LaTeX export Thomas Holst
[not found] <.u63ka5qed@de.bosch.com>
2009-01-20 9:51 ` Carsten Dominik
2009-01-20 8:32 Thomas Holst
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=m2y6qw1zbz.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=Thomas.Holst@de.bosch.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).