From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: TODO type problem on speedbar and imenu. Date: Wed, 24 Aug 2011 16:18:20 +0200 Message-ID: <878vqiubls.fsf@altern.org> References: <8762mwsdhv.fsf@gmail.com> <87vcursd79.fsf@altern.org> <871uwp8vlp.fsf@gmail.com> <87hb5ho0nz.fsf@altern.org> <8762lx6pr5.fsf@gmail.com> <878vqsnhrr.fsf@altern.org> <87liur6h0d.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:43853) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwERh-00030X-5Y for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 10:28:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QwERb-00029T-C2 for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 10:28:45 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:58512) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwERb-00029P-6M for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 10:28:39 -0400 Received: by wyi11 with SMTP id 11so1063481wyi.0 for ; Wed, 24 Aug 2011 07:28:38 -0700 (PDT) In-Reply-To: <87liur6h0d.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 17 Aug 2011 20:16:02 +0200") 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: emacs-orgmode@gnu.org, Osamu OKANO Hi Nicolas, Nicolas Goaziou writes: > I don't mind providing a commit for this, but the list wasn't > exhaustive. I'd rather have a set of rules which would be part of the > Org format specification. Agreed. > What about : allow mixing tabs and spaces only when indenting or > filling. One or more spaces everywhere[1] else. If you feel confident this is flexible enough, please go ahead. We only need to make sure that a task like * TODO Task ^^^^^^ <= unintentional mixed tabs/spaces is okay. In other words: enforce a set of rules, but in a way that will not surprise users if they accidently hit spaces or tabs in position like the end of a line. > An heading regexp would then be: > > "^\\*\\+\\( +TODO\\)?\\( +\\[#.\\]\\)?\\( +.*?\\)?\\([ \t]+\\(:[[:alnum:]]_@#%:\\)\\)?[ \t]*$" > > Note the use of [ \t]+ to fill the tags to the right. Also note that > regexp means "^***" is a valid regexp (which isn't the case actually). Yes, I think keeping "^***" as a valid regexp is a good idea. > [1] As for every rule, some exceptions: check-boxes cookies and > counters, which can be sticked to respectively the headline text and the > check-box. Okay. Thanks for looking again into this when you have some time! -- Bastien