From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: TODO type problem on speedbar and imenu. Date: Wed, 17 Aug 2011 09:30:28 +0200 Message-ID: <82A68A74-84F0-4C21-B34E-CDEA4205F3E5@gmail.com> References: <8762mwsdhv.fsf@gmail.com> <87vcursd79.fsf@altern.org> <871uwp8vlp.fsf@gmail.com> <75CC3431-63F3-4EDA-B65C-C2BEA296FFB7@gmail.com> <87y5yt58wd.fsf@gmail.com> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:43051) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qtaa9-0006dq-UF for emacs-orgmode@gnu.org; Wed, 17 Aug 2011 03:30:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qtaa7-0006Q5-NA for emacs-orgmode@gnu.org; Wed, 17 Aug 2011 03:30:33 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:41952) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qtaa7-0006Pr-IE for emacs-orgmode@gnu.org; Wed, 17 Aug 2011 03:30:31 -0400 Received: by ewy9 with SMTP id 9so317408ewy.0 for ; Wed, 17 Aug 2011 00:30:30 -0700 (PDT) In-Reply-To: <87y5yt58wd.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Bastien , emacs-orgmode@gnu.org, Osamu OKANO On Aug 16, 2011, at 11:44 PM, Nicolas Goaziou wrote: > Hello, > > Carsten Dominik writes: > >> I am not sure this is a good idea. With this patch, you always >> require the space to be there. So "* TODO" would not be a task. >> I am not sure, this might have side effects. > > Notwithstanding the fontification problem, isn't "* TODO" considered as > a valid task, whose text is "TODO" and without a keyword? Well, the behavior is really undefined on these border cases. My worries also stem from the possibility that the match of these regexps now extends an additional character, and there may be places in the code which rely on (match-end 0) being right after (e.g.) the TODO keyword. I do not know if this is the case, but it is a definite possibility. - Carsten