Hello,
Bastien writes:
> Yes, I think keeping "^***" as a valid regexp is a good idea.
In fact, it isn't. "^***" shouldn't match an headline. Not yet
actually. If we want such headlines, org-outline-regexp and al. have to
be set to something like "\\*+". That would break many things, and
outlin
On Aug 24, 2011, at 4:18 PM, Bastien wrote:
> 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 m
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 m
Hello,
Bastien writes:
> Hi Nicolas,
>
> Nicolas Goaziou writes:
>
>> There are quite a few places indeed using "[ \t]" which may use " "
>> instead. Before TODO keywords, before priority cookies, before
>> check-boxes, etc.
>
> Enforcing " " _before_ the places you mention would be good change
Hi Bastien and Nicolas,
Bastien wrote:
> Nicolas Goaziou writes:
>> Notwithstanding the fontification problem, isn't "* TODO" considered
>> as a valid task, whose text is "TODO" and without a keyword?
>
> FWIW, I'm not in favor of this -- I'd rather consider it a task with a
> todo keyword but wi
Hi Nicolas,
Nicolas Goaziou writes:
> There are quite a few places indeed using "[ \t]" which may use " "
> instead. Before TODO keywords, before priority cookies, before
> check-boxes, etc.
Enforcing " " _before_ the places you mention would be good change.
Feel free to commit such a change if
Hi nicolas,
Nicolas Goaziou writes:
> Notwithstanding the fontification problem, isn't "* TODO" considered
> as a valid task, whose text is "TODO" and without a keyword?
FWIW, I'm not in favor of this -- I'd rather consider it a task with a
todo keyword but with no "true headline".
--
Bastie
Hi Carsten and Nicolas,
Carsten Dominik writes:
>> 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.
There are side-effects to the current behavio
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.
>
> Notwithstandin
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
On 13.8.2011, at 12:16, Nicolas Goaziou wrote:
> Hello,
>
> Bastien writes:
>
>> Yep. When you have some free time (!), please suggest a patch and a
>> small org test file so that we can test.
>
> Here is an attempt to convert word boundaries into white spaces where it
> matters.
I am not s
Hello,
Bastien writes:
> Thanks a lot -- I have tested the patch during the last two hours and
> didn't find any problem. Feel free to apply it.
Done.
> What about going one step further and removing the possibility of
> using tabs after TODO keywords?
There are quite a few places indeed us
Hi Nicolas,
Nicolas Goaziou writes:
> Bastien writes:
>
>> Yep. When you have some free time (!), please suggest a patch and a
>> small org test file so that we can test.
>
> Here is an attempt to convert word boundaries into white spaces where it
> matters.
Thanks a lot -- I have tested the
Hello,
Bastien writes:
> Yep. When you have some free time (!), please suggest a patch and a
> small org test file so that we can test.
Here is an attempt to convert word boundaries into white spaces where it
matters.
I paste again the test file from Osamu Okano for reference.
#+begin_src or
Hi Nicolas,
Nicolas Goaziou writes:
> I think it is better to enforce some whitespace after a TODO keyword
> than a word boundary. There are a few places where this could also be
> changed (i.e. `org-complex-heading-regexp-format').
>
> Any opinion on this?
Yep. When you have some free time (!
Hi Nicolas,
Nicolas Goaziou wrote:
> I think it is better to enforce some whitespace after a TODO keyword than a
> word boundary. There are a few places where this could also be changed (i.e.
> `org-complex-heading-regexp-format').
>
> Any opinion on this?
I share your opinion.
Best regards,
S
Hello,
Osamu OKANO writes:
> I found a problem on speedbar and imenu.
> Reproducing date is here
> -8<---cut here---start->8---
> * someday/maybe
> * SOMEDAY/maybe
> * SOMEDAY maybe
> * someday maybe
> * read/review
> * READ/review
> * conf
> #+TYP_TODO: SOMED
17 matches
Mail list logo
