Hello, >>>>> Christian Moe writes:
> Numbers at the beginning of the line inadvertently starting a list > item is a bug. You call it a bug, but it is actually the Org definition of a numbered item. This is in the manual. Though, I think I understand what you mean: this definition can lead to surprising results. But the user is warned in the documentation. > It means you can mess up your exported document (it doesn't just > happen at M-RET) by just writing a perfectly normal text, and there > is no easy-to-remember escape. (I really don't like the > invisible-space workaround -- it's hard to remember how to insert > it, and it's a bizarre trick to have to tell newcomers.) See the solution 1 posted before. This is the "original" solution, although, admittedly, similar problems will resurface with numbers and parenthesis, albeit less frequently. > ReStructuredText provides a backslash-escape for this, even though > its more rigid structure reduces the chances of the error happening. > Could we borrow that trick, or would it conflict with something > else? I don't follow you here. Inserting a non-breaking space (it was only an example, by the way) is an unacceptable trick to tell to newcomers but adding a backslash in front of numbers isn't? It looks the same to me. As long as Org cannot tell between an ordered item and a number at the end of a sentence, those problems will persist. And I can't see any non-hackish solution about it. We can always change `org-plain-list-ordered-item-terminator' default value to the safer ?), though. Regards, -- Nicolas _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
