From: Carsten Dominik <carsten.dominik@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC]: Uniform indentation for lists
Date: Tue, 25 Jun 2013 17:33:38 +0200 [thread overview]
Message-ID: <983E737D-C875-478A-A78A-A2EAEEFBBF78@gmail.com> (raw)
In-Reply-To: <87hagntblh.fsf@gmail.com>
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 <kjambunathan@gmail.com> 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)
>
next prev parent reply other threads:[~2013-06-25 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 21:58 [RFC]: Uniform indentation for lists Jambunathan K
2013-06-25 9:44 ` Suvayu Ali
2013-06-26 4:38 ` Jambunathan K
2013-06-25 15:33 ` Carsten Dominik [this message]
2013-06-25 21:02 ` Achim Gratz
2013-06-26 4:27 ` Jambunathan K
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=983E737D-C875-478A-A78A-A2EAEEFBBF78@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
/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).