emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: why not auto-renumbering list ?
Date: Mon, 09 Aug 2010 13:35:05 +0200	[thread overview]
Message-ID: <87y6cg589i.wl%n.goaziou@gmail.com> (raw)
In-Reply-To: <85E5FB19-8C5A-4436-AB89-65760B565C55@gmail.com>

>>>>> Carsten Dominik writes:

> First, my apologies that I have so far not found the time to test
> your improved list implementation.

No worries, I needed that time anyways, as some internals have
undergone big changes since then. I particularly think about the now
(hopefully) working indent/outdent code, that was quite hairy to

> Have you had any testing feedback from anyone else so far?

Not yet, unfortunately.

> Have you tested it in all the export backends?

Yes, on all major backends: HTML, LaTeX, ASCII and DocBook.

Well, to be honest, in the case of DocBook, I only looked at the xml
produced, and it seems valid to me. For this exporter, changes were
very similar to those applied to the HTML one anyways.

> I don't think anyone sets this to nil.  But there is a use case for
> this, if someone wants some strange specific numbering,
> then it might be useful to allow turning it off.  There is no harm
> in having this possibility.

There's always (in my branch):

2. [@start:2] I like
3. prime numbered
5. [@start:5] lists

It sure is heavy on syntax, but benefit is that every exporter will
reflect that unusual numbering.
> While this sounds reasonable - it also unnecessary to me.
> Why fix something that works?

Because it is not consistent in the current implementation. Please
have this test:

Type the following list in an Org buffer, with
`org-auto-renumber-ordered-lists' set to nil.

10. this is
    1. first sub-item
    2. second sub-item
11. a test
12. list

Now, outdent first sub-item: top-level list gets renumbered, no matter
what. Why? Worse: indentation of second sub-item is now wrong. Undo
the indentation. Now cycle bullets of top level list once, to have
parenthesis instead of dot after the number. There goes the numbering.

And, again, exporters, except ASCII, will not take into consideration
hand-numbered lists. This is not consistent either.

As an intermediate solution, I can make
`org-auto-renumber-ordered-lists' really block all renumbering attempt
while still keeping indentation correct. It won't solve the exporter
problem, though.

I honestly don't think hand-numbering lists is a solution. I know Org
is about simplicity, but [@start:xx] enforced numbers definitely fare
better here. And use cases are, in my opinion, so infrequent that it
will not cripple Org simplicity either.


-- Nicolas

  reply	other threads:[~2010-08-09 11:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07 12:41 why not auto-renumbering list ? Nicolas Goaziou
2010-08-09  6:56 ` Carsten Dominik
2010-08-09 11:35   ` Nicolas Goaziou [this message]
2010-08-09 12:35     ` Nicolas Goaziou
2010-08-10  8:47       ` Andrew Swann
2010-08-10  9:46         ` Nicolas Goaziou
2010-08-10 11:18           ` Andrew Swann
2010-08-10 12:32             ` Nicolas Goaziou
2010-08-11  7:43               ` Andrew Swann

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:

  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=87y6cg589i.wl%n.goaziou@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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