emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: PDF file was not produced! Too deeply nested!??
Date: Mon, 14 May 2012 15:36:47 +0200	[thread overview]
Message-ID: <80sjf2j34g.fsf@somewhere.org> (raw)
In-Reply-To: 5355.1337000954@alphaville

Hi Nick,

Nick Dokos wrote:
> Sebastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> wrote:
>>
>> 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:
>
> \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}

Confirmed...

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

Then, yes, it seems that, somehow, the frametitle is eating 1 nesting level,
leaving just maximum 3 indentation levels for the lists.

One can say that 3 nesting levels is enough for slides (even if the above was
a real case: compiling slides from a colleague), so don't spend time on trying
to understand was the limit is 3 and not 4 levels (and not 6, as falsely
adverted in the FAQ).

Thanks for your help.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2012-05-14 13:36 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
2012-05-14 13:36   ` Sebastien Vauban [this message]
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=80sjf2j34g.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).