From: Nick Dokos <nicholas.dokos@hp.com>
To: Percival du Chat Gris <percyhaven@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Latex error "too deeply nested" only for #+INCLUDE statements
Date: Mon, 15 Oct 2012 17:24:04 -0400 [thread overview]
Message-ID: <4192.1350336244@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Percival du Chat Gris <percyhaven@gmail.com> of "Mon\, 15 Oct 2012 15\:04\:06 EDT." <CA+OpV6kRwcoRUqHBONpS=q-uefZV1DEFk0mAPRqOKzHgbEYPQg@mail.gmail.com>
Percival du Chat Gris <percyhaven@gmail.com> wrote:
>
> ! LaTeX Error: Too deeply nested.
>
> And that repeats over and over again.
>
OK - Seb probably got it right then: if you have too many (too many = 5)
nested itemize environments, latex complains as above.
>
>
> What is the exact output?
>
> Unfortunately there isn't any output.
I meant the error output as you showed above.
>
> What version of org/emacs?
>
> Org-mode: Version : 7.9.2-1
> Emacs: Version : 23.3.a-3
>
OK.
> Are you using the new exporter or the old exporter?
>
> How would I be able to tell?
C-c C-e p invokes the old exporter. To use the new exporter,
see for example this thread:
http://thread.gmane.org/gmane.emacs.orgmode/60236/focus=61566
> If the error is produced by latex, export to latex and look at the .tex
> file. If the error is produced by org, it
> would help to have a backtrace.
>
> Well ... I presume the error is produced by Latex, because I can get the same thing if I run LaTex Export.tex, but if I replace all the
> #+INCLUDE references with the contents of the files themselves, in the .org file, it works, so I think it's an .org problem, in
> producing the .tex files, not (necessarily) a LaTex problem.
>
I would strip down the contents of the files to just the headers: it's the
structure that matters here, not the details. Then I would ask the exporter
to export to latex and compare the tex files by opening them in two side-by-side
windows in emacs: the differences should be telling.
> I think (not being an expert) it seems that, with the stub-based file (Export.tex), the single * in each of the #+INCLUDEed files
> becomes a subsection, as opposed to an actual section (as it did in Export-1.tex), since a section of the diff file between the .tex
> files produced looks something like:
>
> diff Export.tex Export-1.tex
> [...]
> 1144a1132,1133
> > \subsection{Dynamic Interactions}
> > \label{sec-7-5}
> 1146,1147d1134
> < \item Dynamic Interactions\\
> < \label{sec-1-1-4-5-1-6-5-1-10-5-1-4-5-1-4-5-1-5}%
The differences *are* telling: In one case, you have a subsection at
level 2, in the other an item at level (almost) infinity :-)
> 1154c1141
> < \label{sec-1-1-4-5-1-6-5-1-10-5-1-4-5-1-4-5-1-5-1}%
> ---
> > \label{sec-7-5-1}%
> 1157c1144
> < \label{sec-1-1-4-5-1-6-5-1-10-5-1-4-5-1-4-5-1-5-2}%
> ---
> > \label{sec-7-5-2}%
> 1160c1147
> < \label{sec-1-1-4-5-1-6-5-1-10-5-1-4-5-1-4-5-1-5-3}%
> ---
> > \label{sec-7-5-3}%
> 1163c1150
> < \label{sec-1-1-4-5-1-6-5-1-10-5-1-4-5-1-4-5-1-5-4}%
> ---
> > \label{sec-7-5-4}%
> 1166c1153
> [...]
>
> I attach a tarball with a simple example where the new exporter with
>
> Org-mode version 7.9.2 (release_7.9.2-432-g545166 @ /home/nick/elisp/org-mode/lisp/)
> GNU Emacs 24.2.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.4) of 2012-09-21
>
> Thank you, I will try it, and see if that will clear up the issue.
>
>
> does the right thing.
BTW, I think the old exporter mishandles my simple example (and slightly
modified variants) in various ways. I would recommend that you try the
new exporter at this point.
Nick
prev parent reply other threads:[~2012-10-15 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 16:55 Latex error "too deeply nested" only for #+INCLUDE statements Percival du Chat Gris
2012-10-15 18:20 ` Sebastien Vauban
2012-10-15 18:24 ` Nick Dokos
2012-10-15 19:04 ` Percival du Chat Gris
2012-10-15 21:24 ` Nick Dokos [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
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=4192.1350336244@alphaville.americas.hpqcorp.net \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=percyhaven@gmail.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 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).