From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: [PATCH] Alphabetical ordered lists Date: Tue, 28 Sep 2010 18:12:55 +0200 Message-ID: References: <87bp8o498o.fsf@gollum.intra.norang.ca> <393C5110-E4D3-4B36-8F4E-4F94B5AA0F93@gmail.com> <87k4m876g3.wl%n.goaziou@gmail.com> <87iq1r7k00.wl%n.goaziou@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=36486 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P0dTM-0007p0-KX for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 12:56:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1P0dTK-0006tg-AE for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 12:56:08 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:39375) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P0dTK-0006tU-5w for emacs-orgmode@gnu.org; Tue, 28 Sep 2010 12:56:06 -0400 Received: by eyh5 with SMTP id 5so2359596eyh.0 for ; Tue, 28 Sep 2010 09:56:05 -0700 (PDT) In-Reply-To: <87iq1r7k00.wl%n.goaziou@gmail.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: Nicolas Goaziou Cc: Bernt Hansen , emacs-orgmode@gnu.org, Jacob Mitchell On Sep 27, 2010, at 8:55 AM, Nicolas Goaziou wrote: >>>>>> Nathaniel Flath writes: > >>> But, there is apparently one major drawback, as I said in a >>> previous post. If the line starts with a word followed by a dot or >>> a parenthesis, Org will see a bullet there. This is bad news >>> because the following line will be indented, or a M-RET will delete >>> the word, replacing it with a) or a. > >> Yes, this happens - it's not something that comes up during my >> normal usage, so I didn't notice. Can you think of a way to >> determine if this is the case vs. a list is actually wanted? > > Unfortunately, I can't see anything clean. This is tricky because > lists are the closest construct to raw text. My feeling is that we should not apply this patch. I see how it might be nice to have such lists - but confusion is rather likely in this case. - Carsten