emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: incorrect export for LaTeX [8.2.10 (release_8.2.10 @ c:/emacs25-91/share/emacs/25.0.91/lisp/org/)]
Date: Sun, 06 Mar 2016 20:57:12 +0100	[thread overview]
Message-ID: <87bn6rz8fb.fsf@mbork.pl> (raw)
In-Reply-To: <87d1rco9v1.fsf@gmx.us>


On 2016-03-02, at 22:20, Rasmus <rasmus@gmx.us> wrote:

>> Fair enough. Do you have a proposal for deeply nested headlines (or
>> items)?
>
> Use this header:
>
> #+options: h:0
> #+latex_header: \usepackage{enumitem}
> #+latex_header: \setlistdepth{9}
> #+latex_header: \setlist[enumerate]{label=(\arabic*)}
>
>
> I don’t think we need to do anything.  If we wanted to support this we’d
> probably need to load enumerate (which is not a bad package...).  We have
> worse offenders of manual config.  Local TOCs spring to mind.
> http://orgmode.org/org.html#fn-113

I've just seen this thread, and decided to chime in.  I think that the
situation is fine: such deep nesting of lists should be _actively
discouraged_ IMHO.

While list support in LaTeX is IMO suboptimal (to say the least), and
enumitem is a must for me in most of my documents, four levels of
nesting is even too many (by a factor of 2).  My opinion is that base
LaTeX should limit the nesting to two levels, and a special package
(like enumitem) should be needed to cater for those really strange
documents that need more.  (Yes, they do exist, but are very rare
I believe.)

> Rasmus

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

  parent reply	other threads:[~2016-03-06 19:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 15:31 Bug: incorrect export for LaTeX [8.2.10 (release_8.2.10 @ c:/emacs25-91/share/emacs/25.0.91/lisp/org/)] 9661031
2016-02-29 21:16 ` Nicolas Goaziou
2016-03-02 21:20   ` Rasmus
2016-03-04  0:13     ` Nicolas Goaziou
2016-03-04 16:48       ` Nick Dokos
2016-03-06 19:07         ` Rasmus
2016-03-06 19:32           ` Nick Dokos
2016-03-06 19:57             ` Rasmus
2016-03-06 18:57       ` Rasmus
2016-03-07 11:12         ` Nicolas Goaziou
2016-03-07 13:35           ` Rasmus
2016-03-07 21:51             ` Nicolas Goaziou
2016-03-06 19:57     ` Marcin Borkowski [this message]
2016-03-14 11:05   ` 9661031

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=87bn6rz8fb.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).