From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Latex error "too deeply nested" only for #+INCLUDE statements
Date: Mon, 15 Oct 2012 20:20:17 +0200 [thread overview]
Message-ID: <80pq4jtx5q.fsf@somewhere.org> (raw)
In-Reply-To: CA+OpV6=coUMyRda7jDDtaGHnhUyVHr8ZUpvBJwqjV17pnm9-PA@mail.gmail.com
Hello Percival,
Percival du Chat Gris wrote:
> I've tried googling, reading faqs and the like, and have come up empty.
>
> If I have a number of stub files, with the information in them that I want
> to pull into multiple documents, and I #+INCLUDE them in a file, I get the
> latex "too deeply nested" error. If, however, I simply insert the files
> into the buffer, then they will create the PDF via latex export without a
> problem. Is there something in the #+INCLUDE code that adds a nested layer
> such that it becomes problematic for PDF production? If so, is there a
> better route to create PDF files? I have been using Latex and HTML export
> for a while, so I'm not entirely familiar with any other options that might
> produce PDF files as cleanly. While I can (and have) written a script to
> pull all the pieces together into one large file, there should be an easier
> way.
It makes me think at lists of levels 5 or more. Are you including your source
files at deep levels?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-10-15 18:20 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 [this message]
2012-10-15 18:24 ` Nick Dokos
2012-10-15 19:04 ` Percival du Chat Gris
2012-10-15 21:24 ` Nick Dokos
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=80pq4jtx5q.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).