From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>,
Osamu OKANO <okano.osamu@gmail.com>
Subject: Re: TODO type problem on speedbar and imenu.
Date: Wed, 24 Aug 2011 16:37:01 +0200 [thread overview]
Message-ID: <3ECF6EA9-213B-4B98-90F4-B5C034010D46@gmail.com> (raw)
In-Reply-To: <878vqiubls.fsf@altern.org>
On Aug 24, 2011, at 4:18 PM, Bastien wrote:
> Hi Nicolas,
>
> Nicolas Goaziou <n.goaziou@gmail.com> 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.
Hi Nicolas
Org currently also uses \t before the tags, when it aligns them.
- Carsten
>
> 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
>
- Carsten
next prev parent reply other threads:[~2011-08-24 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 12:51 TODO type problem on speedbar and imenu Osamu OKANO
2010-07-23 9:06 ` Noorul Islam K M
2010-07-24 21:38 ` Sébastien Vauban
2010-07-25 11:48 ` Osamu OKANO
2010-08-01 12:50 ` David Maus
2011-07-21 0:07 ` Nicolas Goaziou
2011-07-21 7:19 ` Sebastien Vauban
2011-07-24 19:00 ` Bastien
2011-08-13 10:16 ` Nicolas Goaziou
2011-08-16 14:47 ` Bastien
2011-08-16 20:54 ` Nicolas Goaziou
2011-08-17 16:00 ` Bastien
2011-08-17 18:16 ` Nicolas Goaziou
2011-08-24 14:18 ` Bastien
2011-08-24 14:37 ` Carsten Dominik [this message]
2011-08-25 0:31 ` Nicolas Goaziou
2011-08-16 21:07 ` Carsten Dominik
2011-08-16 21:44 ` Nicolas Goaziou
2011-08-17 7:30 ` Carsten Dominik
2011-08-17 16:07 ` Bastien
2011-08-17 15:57 ` Bastien
2011-08-17 17:45 ` Sebastien Vauban
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ECF6EA9-213B-4B98-90F4-B5C034010D46@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=okano.osamu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).