public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Ulrike Fischer <luatex-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: LaTeX Error: Too deeply nested
Date: Fri, 10 Nov 2023 20:18:01 +0100	[thread overview]
Message-ID: <5inl7wuxy962.dlg@nililand.de> (raw)
In-Reply-To: <dc6f918b-26aa-49ad-a69b-01d5c98cb938n@googlegroups.com>

Am Wed, 8 Nov 2023 23:22:07 -0800 (PST) schrieb 'Martin Ehlers' via
pandoc-discuss:

> When converting a markdown document to PDF using Pandoc, I get an error 
> saying:
> 
> ! LaTeX Error: Too deeply nested.
> 
> According to some documentation and discussions, this error relates to 
> nested lists, however I am not using any nested list. What else might cause 
> this issue?

You could use a list without knowing. A number of environments are
internally lists, e.g. quote or environments which change margins.

If you could show the LaTeX code it would be probably quite trivial
to find out where the error is from. 

-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/


      parent reply	other threads:[~2023-11-10 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09  7:22 'Martin Ehlers' via pandoc-discuss
     [not found] ` <dc6f918b-26aa-49ad-a69b-01d5c98cb938n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-09  8:45   ` Guillaume Dehaene
     [not found]     ` <CAKOoOVUvuvX7_yMV9+OpbkpCZod3pLVVfgSXxVH_eiL=DyHLuA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-10 10:35       ` 'Martin Ehlers' via pandoc-discuss
2023-11-10 19:18 ` Ulrike Fischer [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5inl7wuxy962.dlg@nililand.de \
    --to=luatex-bmiygyzgj3ab1svskn2v4q@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@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.
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 NNTP newsgroup(s).