emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 14:24:46 -0400	[thread overview]
Message-ID: <10695.1350325486@alphaville> (raw)
In-Reply-To: Message from Percival du Chat Gris <percyhaven@gmail.com> of "Mon\, 15 Oct 2012 12\:55\:31 EDT." <CA+OpV6=coUMyRda7jDDtaGHnhUyVHr8ZUpvBJwqjV17pnm9-PA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]

Percival du Chat Gris <percyhaven@gmail.com> wrote:

> Good day,
> 
> 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. 

Please provide details and, if possible, a minimal example.

Who produces this error? What is the exact output? What version of org/emacs?
Are you using the new exporter or the old exporter?

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.

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

does the right thing.

Nick

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


[-- Attachment #2: doc.org and three included files --]
[-- Type: application/x-gzip, Size: 537 bytes --]

  parent reply	other threads:[~2012-10-15 18: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 [this message]
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=10695.1350325486@alphaville \
    --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).