From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [BUG] adding new plain lists item changes previous one it it ends in a number on a single lijne followed by a dot Date: Thu, 03 Feb 2011 15:09:52 +0100 Message-ID: <877hdh6wgf.wl%n.goaziou@gmail.com> References: <20110202192020.GF5402@shi.workgroup> <87bp2u6stl.wl%n.goaziou@gmail.com> <4D4A7F61.4010202@christianmoe.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from [140.186.70.92] (port=41610 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pkzsl-0006YM-IA for emacs-orgmode@gnu.org; Thu, 03 Feb 2011 09:10:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pkzsk-0008S6-FF for emacs-orgmode@gnu.org; Thu, 03 Feb 2011 09:09:59 -0500 Received: from mail-ey0-f169.google.com ([209.85.215.169]:43882) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pkzsk-0008S2-Ap for emacs-orgmode@gnu.org; Thu, 03 Feb 2011 09:09:58 -0500 Received: by eyh6 with SMTP id 6so583377eyh.0 for ; Thu, 03 Feb 2011 06:09:57 -0800 (PST) In-Reply-To: <4D4A7F61.4010202@christianmoe.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: mail@christianmoe.com Cc: emacs-orgmode 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