From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz 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 19:04:20 +0100 Message-ID: <87lj1x0zbv.fsf@Rainer.invalid> References: <20110202192020.GF5402@shi.workgroup> <87bp2u6stl.wl%n.goaziou@gmail.com> <4D4A7F61.4010202@christianmoe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=40135 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pl3Xs-0000Rf-3Y for emacs-orgmode@gnu.org; Thu, 03 Feb 2011 13:04:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pl3Xr-0000V0-0f for emacs-orgmode@gnu.org; Thu, 03 Feb 2011 13:04:40 -0500 Received: from lo.gmane.org ([80.91.229.12]:41762) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pl3Xq-0000Ug-N7 for emacs-orgmode@gnu.org; Thu, 03 Feb 2011 13:04:38 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Pl3Xm-0000MG-BH for emacs-orgmode@gnu.org; Thu, 03 Feb 2011 19:04:34 +0100 Received: from p57aaafa3.dip.t-dialin.net ([87.170.175.163]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Feb 2011 19:04:34 +0100 Received: from Stromeko by p57aaafa3.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Feb 2011 19:04:34 +0100 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: emacs-orgmode@gnu.org Christian Moe writes: > For once, I have to disagree: Numbers at the beginning of the line > inadvertently starting a list item is a bug. Something that is a direct result of the specification can't be usefully called a bug of the implementation. It may still be unexpected and/or unwanted behaviour, so I like to call it an accidental feature. Please not that it can (by specification) happen to other list constructs just as well - and given the chance, it will. Let me try: --8<---------------cut here---------------start------------->8--- 1. This is an awfully constructed example of how I might mess up (1, 2, 3) - oops, I just did. I might have triggered a different accidental feature if my linewrap would have been set two columns later. How's that looking to you? --8<---------------cut here---------------end--------------->8--- > 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.) Again, this is the result of syntactic convenience for the common case. This sort of thing tends to break less common cases, which is precisely the reason TeX macros are sprinkled with seemingly superfluous {} at every conceivable word boundary. Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds