From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: TODO type problem on speedbar and imenu. Date: Wed, 24 Aug 2011 16:37:01 +0200 Message-ID: <3ECF6EA9-213B-4B98-90F4-B5C034010D46@gmail.com> 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> <878vqiubls.fsf@altern.org> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:38331) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwEZn-0005aq-Gg for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 10:37:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QwEZm-0003jh-7K for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 10:37:07 -0400 Received: from mail-ey0-f171.google.com ([209.85.215.171]:40506) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwEZl-0003jY-Vf for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 10:37:06 -0400 Received: by eyg24 with SMTP id 24so1148768eyg.30 for ; Wed, 24 Aug 2011 07:37:04 -0700 (PDT) In-Reply-To: <878vqiubls.fsf@altern.org> 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: Bastien Cc: emacs-orgmode@gnu.org, Nicolas Goaziou , Osamu OKANO On Aug 24, 2011, at 4:18 PM, Bastien wrote: > Hi Nicolas, >=20 > Nicolas Goaziou writes: >=20 >> 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. >=20 > Agreed. >=20 >> What about : allow mixing tabs and spaces only when indenting or >> filling. One or more spaces everywhere[1] else. Hi Nicolas Org currently also uses \t before the tags, when it aligns them. - Carsten >=20 > If you feel confident this is flexible enough, please go ahead. > We only need to make sure that a task like >=20 > * TODO Task =20 > ^^^^^^ <=3D unintentional mixed tabs/spaces >=20 > 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. >=20 >> An heading regexp would then be: >>=20 >> "^\\*\\+\\( +TODO\\)?\\( +\\[#.\\]\\)?\\( +.*?\\)?\\([ = \t]+\\(:[[:alnum:]]_@#%:\\)\\)?[ \t]*$" >>=20 >> 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). >=20 > Yes, I think keeping "^***" as a valid regexp is a good idea. >=20 >> [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. >=20 > Okay. >=20 > Thanks for looking again into this when you have some time! >=20 > --=20 > Bastien >=20 - Carsten