emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Scott Otterson <scotto@sharpleaf.org>
Cc: "Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Latex export fails for plain lists deeper than four, works for html
Date: Sat, 03 Dec 2016 22:10:07 +0100	[thread overview]
Message-ID: <871sxod8i8.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAPY3P0S+QZz3x_hpo_eCMUpdDGJ7Vjz+FEQBAN_DxizYGY8Gcg@mail.gmail.com> (Scott Otterson's message of "Sat, 3 Dec 2016 17:45:09 +0100")

Hello,

Scott Otterson <scotto@sharpleaf.org> writes:

> If a plain list has more than four levels, org-mode will produce latex that
> crashes.  See attached.  On the other hand, html export works fine, even
> for much deeper lists.
>
> In a large org file, this export error is pretty time consuming for a naive
> user (me) to isolate, so I'd like to suggest that, before crashing latexmk,
> org-mode should at least print a human-readable warning -- especially since
> deep list export works for other export types.
>
> Better yet, would be deeper latex lists.  There are ways:
>
> http://tex.stackexchange.com/questions/41408/a-five-level-deep-list
> 1. level 1.1
>    1. level 2.1
>       1. level 3.1
>          1. level 4.1
>             1. level 5.1 (works if this level is deleted)
>             2. level 5.2 (works if this level is deleted)
>          2. level 4.2
>       2. level 3.2
>    2. level 2.2
> 2. level 1.2

Again, this doesn't crash here. 

Also, the manual already gives hint about how to support more than four
levels of nesting for lists.

Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2016-12-03 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03 16:45 Latex export fails for plain lists deeper than four, works for html Scott Otterson
2016-12-03 21:10 ` Nicolas Goaziou [this message]
2016-12-05  8:30   ` Scott Otterson
2016-12-07 11:26     ` Nicolas Goaziou

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=871sxod8i8.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=scotto@sharpleaf.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

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