From: Nick Dokos <nicholas.dokos@hp.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: PDF file was not produced! Too deeply nested!??
Date: Mon, 14 May 2012 09:09:14 -0400 [thread overview]
Message-ID: <5355.1337000954@alphaville> (raw)
In-Reply-To: Message from "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> of "Mon, 14 May 2012 14:35:28 +0200." <801umnj5yn.fsf@somewhere.org>
Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> Hello,
>
> With the following Org-Beamer ECM, I've got a "too deeply nested" error.
>
> #+TITLE: PDF file was not produced!
> #+AUTHOR: Seb Vauban
> #+DATE: 2012-05-14
> #+Time-stamp: <2012-05-14 Mon 14:32 Fabrice on MEDIACENTER>
>
> #+LaTeX_CLASS: beamer
> #+LaTeX_CLASS_OPTIONS: [presentation,t]
> #+BEAMER_HEADER_EXTRA: \usetheme{default}\usecolortheme{default}
> #+BEAMER_FRAME_LEVEL: 1
>
> * Action plan
>
> ** Iterations on architecture
>
> - 2-tier
> + Fat client
> + MySQL DB
>
> - 2-tier vers 3-tier
> + Analysis of the separation
> * What logic at which place?
> * Which data, where?
> + Impact on performance
>
> ** Iterations on ...
>
> On http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep, they say:
>
> "LaTeX keeps track of the nesting of one list inside another. There is a
> set of list formatting parameters built-in for application to each of the
> list nesting levels; the parameters determine indentation, item
> separation, and so on. The list environment (the basis for list
> environments like itemize and enumerate) "knows" there are only 6 of these
> sets."
>
> But, here, I only have 4 indentation levels (the level 2 "Iterations on
> architecture" being an item as well, as BEAMER_FRAME_LEVEL is 1).
>
> If I remove:
>
> * What logic at which place?
> * Which data, where?
>
> then I only have 3 levels, and everything compiles right.
>
> But with that 4-th level (far from 6!), the compilation simply ends in error.
>
> Anyone understanding why this happens?
>
Apparently the FAQ is wrong: 4 will compile, 5 will not - e.g. the
following will not compile with my setup:
--8<---------------cut here---------------start------------->8---
\documentclass{article}
\begin{document}
\begin{itemize}
\item foo
\begin{itemize}
\item bar
\begin{itemize}
\item baz
\begin{itemize}
\item hunoz
\begin{itemize}
\item hukerz
\end{itemize}
\end{itemize}
\end{itemize}
\end{itemize}
\end{itemize}
\end{document}
--8<---------------cut here---------------end--------------->8---
That's probably part of the explanation - the extra frame enclosing the
nested list in your case might have something to do with the rest but
that's purely a guess.
Nick
next prev parent reply other threads:[~2012-05-14 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 12:35 PDF file was not produced! Too deeply nested!?? Sebastien Vauban
2012-05-14 13:09 ` Nick Dokos [this message]
2012-05-14 13:36 ` Sebastien Vauban
2012-05-14 15:17 ` Bastien
2012-05-14 19:29 ` Sebastien Vauban
2012-05-14 19:43 ` Bastien
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=5355.1337000954@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).