emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Martin Weigele <martin@weigele.de>
To: emacs-orgmode@gnu.org
Subject: Re: Strange behaviour of produced latex-pdf
Date: Wed, 2 Feb 2011 23:53:05 +0100	[thread overview]
Message-ID: <201102022353.06165.martin@weigele.de> (raw)
In-Reply-To: <87r5bqgjk2.fsf@ucl.ac.uk>

Am Mittwoch, 2. Februar 2011, um 23:26:05 schrieb Eric S Fraga:
> "Thomas S. Dye" <tsd@tsdye.com> writes:
> > On Feb 2, 2011, at 1:30 AM, Martin Weigele wrote:
> >> Dear all, have encountered the following strange behaviour in
> >> producing latex-
> >> pdf from a standard outline, C-c C-e d . One of many top nodes is
> >> seemingly
> >> arbitrarily not broken down into subnodes. It works fine, however,
> >> when
> >> producing html. Emacs 23.1.1; org-7.4 manually installed; ubuntu
> >> 10.04 LTS.
> 
> [...]
> 
> >> Like others, the unrefined chapter contains only (sub)headlines, no
> >> text yet.
> >> Any ideas?
> > 
> > Aloha Martin,
> > 
> > I don't understand what you mean by "not broken down."  Could you
> > provide an example of the LaTeX output?
> 
> I also do not necessarily understand what is meant by that but I can say
> that I recently had some problems with the latex exporter, especially
> over the weekend, not exporting the full document the way I would have
> expected: whole sub-trees did not get exported to the latex although
> they did come out in an HTML export, for instance.
> 
> Unfortunately, I was unable to reproduce this problem with a small
> example and the document where it was exhibited is large and
> definitely not distributable.
> 
> Fortunately, the problem seems to have disappeared and my latex export
> works just fine now -- and the document has not changed (it's under
> revision control).
> 
> So, I can suggest to Martin: upgrade to the latest git version of org
> and see if that helps?
> 
> eric

Thanks Eric, it appears that the fact that a whole subtree indeed disappeared 
from the latex output had left me kind of "speechless" :-) . No the problem 
does not go away with latest git sources.
Martin

next prev parent reply	other threads:[~2011-02-02 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 11:30 Strange behaviour of produced latex-pdf Martin Weigele
2011-02-02 16:38 ` Thomas S. Dye
2011-02-02 22:26   ` Eric S Fraga
2011-02-02 22:53     ` Martin Weigele [this message]
2011-02-02 23:06       ` Thomas S. Dye
2011-02-03  0:23         ` Eric S Fraga
2011-02-02 23:44       ` Martin Weigele

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=201102022353.06165.martin@weigele.de \
    --to=martin@weigele.de \
    --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

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).