From: Scott Otterson <scotto@sharpleaf.org>
To: Scott Otterson <scotto@sharpleaf.org>,
"Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Latex export fails for plain lists deeper than four, works for html
Date: Mon, 5 Dec 2016 09:30:11 +0100 [thread overview]
Message-ID: <CAPY3P0Q-Lifph_aPJ8Z+Bqht2T6bN-Mqr+0ikCFL9YuiZLz_Sw@mail.gmail.com> (raw)
In-Reply-To: <871sxod8i8.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
Hi Nicolas, thanks for trying to replicate this on Linux. What happens for
you if it doesn't crash? Does the latex export just work and produce a pdf
with a set of properly nested lists?
Would you be willing to sent me .tex your latex export produces? It seems
unlikely, but maybe org use a different/additional latex library on Linux
than it does in Windows. Or alternatively, TexLive installs different/more
libraries on Windows. Anyway, it would be nice to figure it out.
I googled quickly for the hint you mentioned but couldn't find it.
On Sat, Dec 3, 2016 at 10:10 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> 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
>
[-- Attachment #2: Type: text/html, Size: 2654 bytes --]
next prev parent reply other threads:[~2016-12-05 8:31 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
2016-12-05 8:30 ` Scott Otterson [this message]
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=CAPY3P0Q-Lifph_aPJ8Z+Bqht2T6bN-Mqr+0ikCFL9YuiZLz_Sw@mail.gmail.com \
--to=scotto@sharpleaf.org \
--cc=emacs-orgmode@gnu.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).