From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: [PATCH] Alphabetical ordered lists Date: Wed, 29 Sep 2010 17:49:44 +0200 Message-ID: <747F5104-6B1C-43E8-BF42-883287B7E303@gmail.com> 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=49852 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P0yuj-0005mK-PQ for emacs-orgmode@gnu.org; Wed, 29 Sep 2010 11:49:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1P0yui-0000IZ-Ie for emacs-orgmode@gnu.org; Wed, 29 Sep 2010 11:49:49 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:62454) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P0yui-0000ID-C3 for emacs-orgmode@gnu.org; Wed, 29 Sep 2010 11:49:48 -0400 Received: by ewy19 with SMTP id 19so363081ewy.0 for ; Wed, 29 Sep 2010 08:49:47 -0700 (PDT) In-Reply-To: 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: Carsten Dominik Cc: Bernt Hansen , emacs-orgmode@gnu.org, Nicolas Goaziou , Jacob Mitchell On Sep 28, 2010, at 6:12 PM, Carsten Dominik wrote: > > 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. Or, alternatively, put it in with an option to turn it on (default off, I think). And maybe we should after all limit it to a single character to avoid confusion. Yes, I do realise that I asked for several characters - but I am learning... - Carsten > > - Carsten >