[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [RFC]: Uniform indentation for lists
From: |
Carsten Dominik |
Subject: |
Re: [O] [RFC]: Uniform indentation for lists |
Date: |
Tue, 25 Jun 2013 17:33:38 +0200 |
Hi,
the indentation rules for lists in Org are ancient, and I don't thing we
want to break so many existing files. And we certainly cannot change the
numbered bullets.
The only thing I would accept is an option to enforce 3 space indentation
on TAB, but the parser must read 2 space indentation as well. And, as
Savayu points out, lists longer than 9 items will always be an issue.
- Carsten
On 24.6.2013, at 23:58, Jambunathan K <address@hidden> wrote:
>
> This request is a result of adding Org-mode support to Oddmuse. (See my
> earlier mail that introduces Orgmuse).
>
> When lists are "normalized", the sub-lists are introduced by varying
> amout of spaces depending on the type of the parent list. It's 3 spaces
> if the parent is numbered and 2 spaces if the parent is bulleted.
>
> 1. One
> 2. Two
> - Bullet One
> - Bullet Two
> 1. One
> 2. Two
>
> Oddmuse wiki and possibly Usemod (and even other Wiki engines) do a
> linear scan of text (much like what the old org-html.el used to do) and
> emits HTML by looking at thing at point. Having the list items
> introduced by varying amout of spaces makes the parser "more" stateful.
>
> I was wondering whether there would be some interest in
>
> 1) To eliminate the separators - "." or ")" - in the numbered list
> 2) Enhance the list repair routine so that it will alway indent by 3 spaces.
>
> With (1) above, the earlier list becomes,
>
> 1 One
> 2 Two
> - Bullet One
> - Bullet Two
> 1 One
> 2 Two
>
> This gives a uniform indentation of 2 spaces.
>
>
> With (2) or (3), the earlier list becomes,
>
> 1. One
> 2. Two
> - Bullet One
> - Bullet Two
> 1. One
> 2. Two
>
> This gives an indentation of 3 spaces. The 3 spaces could either be
> mandated by the canonical Org-markup spec or it could be ensured by the
> author of Org document himself (by using the proposed new repair option)
>