Can't use char ">" in TODO state

Can't use char ">" in TODO state

[Sebastien Vauban]

#+SEQ_TODO: NEW> TEST DONE CANX

Hello,

Instead of using the TODO state "NEW", I tried using "NEW>" so that it
occupies 4 letters, as all my other states (better display in the agenda).

Though...

* TEST Do this

Simply use S-right arrow to cycle through the different states, and you'll see
"NEW>" added many times:

- DONE Do this
- CANX Do this
- Do this
- NEW> Do this

  which "prooves" that "NEW>" is well somehow considered as a TODO state,
  being added automagically, but the next cycle steps don't succeed...

- NEW> NEW> Do this
- NEW> NEW> NEW> Do this
- ...

I find this behavior not entirely satisfying, even if I can fully accept that
">" is a forbidden character in the TODO states. For example, we could think
of a warning being generated, or of the state being fully ignored, or ...

BTW, do you have an alternative for this "NEW" state, in 4 positions? ;-)

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Can't use char ">" in TODO state

[Michael Brand]

Hi Sebastien

On Tue, Oct 18, 2011 at 12:32, Sebastien Vauban
> Instead of using the TODO state "NEW", I tried using "NEW>" so that it
> occupies 4 letters, as all my other states (better display in the agenda).
>
> Though...
>
> * TEST Do this
>
> Simply use S-right arrow to cycle through the different states, and you'll see
> "NEW>" added many times:
>
> - DONE Do this
> - CANX Do this
> - Do this
> - NEW> Do this
>
>  which "prooves" that "NEW>" is well somehow considered as a TODO state,
>  being added automagically, but the next cycle steps don't succeed...
>
> - NEW> NEW> Do this
> - NEW> NEW> NEW> Do this
> - ...
>
> I find this behavior not entirely satisfying, even if I can fully accept that
> ">" is a forbidden character in the TODO states. For example, we could think
> of a warning being generated, or of the state being fully ignored, or ...

It works with this patch
http://patchwork.newartisans.com/patch/964
from Nicolas which I am still using to test it.

> BTW, do you have an alternative for this "NEW" state, in 4 positions? ;-)

What about NEVV ?  (ok, it was a joke)

Michael

Re: Can't use char ">" in TODO state

[Bastien]

Hi,

Michael Brand <michael.ch.brand@gmail.com> writes:

> It works with this patch
> http://patchwork.newartisans.com/patch/964
> from Nicolas which I am still using to test it.

Has anyone else been using this patch without problems?

If so, then Nicolas please apply it.  It really simplifies
the way headlines are matched in many places in the code.

Thanks,

-- 
 Bastien

Re: Can't use char ">" in TODO state

[Nicolas Goaziou]

Hello,

Bastien <bzg@altern.org> writes:

> Michael Brand <michael.ch.brand@gmail.com> writes:
>
>> It works with this patch
>> http://patchwork.newartisans.com/patch/964
>> from Nicolas which I am still using to test it.

> If so, then Nicolas please apply it.  It really simplifies
> the way headlines are matched in many places in the code.

I've applied it.

Regards,

-- 
Nicolas Goaziou

Re: Can't use char ">" in TODO state

[Jambunathan K]

[-- Attachment #1: Type: text/plain, Size: 394 bytes --]


Note the regression in TOC with this commit. The HTML file was produced
by C-C C-e b (by org-html.el) with emacs -Q.

,----
| commit dfcb6faef11a2439b56b18a6289803361d402130
| Author: Nicolas Goaziou <n.goaziou@gmail.com>
| Date:   Thu Aug 25 01:58:29 2011 +0200
| 
|     Provide more consistent regexps for headlines
|     
`----

This is also creating a regression in the ODT exporter.

-- 

[-- Attachment #2: test.html --]
[-- Type: text/html, Size: 4238 bytes --]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: test.org --]
[-- Type: text/x-org, Size: 576 bytes --]

#+TITLE: Testfile for OpenDocumentText Exporter
#+AUTHOR:    Jambunathan K
#+EMAIL:     kjambunathan@gmail.com
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE:  en
#+OPTIONS:   H:4 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc

#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+XSLT:
#+STARTUP: overview


# Use C-c C-e O or C-c C-e o to export this buffer to OpenDocumentText

* Sample Content (Proof Of Concept)
** Character Styles
*** Bold

    *This is bold text*

Re: Can't use char ">" in TODO state

[Nicolas Goaziou]

Jambunathan K <kjambunathan@gmail.com> writes:

> Note the regression in TOC with this commit. The HTML file was produced
> by C-C C-e b (by org-html.el) with emacs -Q.

I think this should be fixed now.

Regards,

-- 
Nicolas Goaziou

Re: Can't use char ">" in TODO state

[Bastien]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

>> If so, then Nicolas please apply it.  It really simplifies
>> the way headlines are matched in many places in the code.
>
> I've applied it.

Thanks a lot.

-- 
 Bastien

Re: Can't use char ">" in TODO state

[Sebastien Vauban]

Hi Nicolas,

Nicolas Goaziou wrote:
> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>> Michael Brand <michael.ch.brand-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> It works with this patch
>>> http://patchwork.newartisans.com/patch/964
>>> from Nicolas which I am still using to test it.
>
>> If so, then Nicolas please apply it.  It really simplifies
>> the way headlines are matched in many places in the code.
>
> I've applied it.

This works as expected from my point of view.
Thanks a lot...

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Can't use char ">" in TODO state

[Sebastien Vauban]

Hi Nicolas and Bastien,

> Nicolas Goaziou wrote:
>> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>>> Michael Brand <michael.ch.brand-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>>
>>>> It works with this patch
>>>> http://patchwork.newartisans.com/patch/964
>>>> from Nicolas which I am still using to test it.
>>
>>> If so, then Nicolas please apply it.  It really simplifies
>>> the way headlines are matched in many places in the code.
>>
>> I've applied it.
>
> This works as expected from my point of view. Thanks a lot...

... with this exception (when using TODO states from Dan Davison):

#+OPTIONS:   ^:nil
#+SEQ_TODO: DOESN'T_WORK DOESN'T-WORK | WORKS

* WORKS Marche

In HTML, class is "WORKS" and word in the heading is "WORKS" as well.

* DOESN'T_WORK Marche pas

The HTML class is "DOESN'T_WORK" (the real name of the state) and
"DOESN_T_WORK" in the heading.

In LaTeX, the status "DOESN'T_WORK" is kept as-is in the heading, hence
provoking a layout bug in the PDF.

This is true, whatever the value of the option ^ for interpreting sub- and
super-scripts: setting it to =t= or to =nil= makes no difference.

* DOESN'T-WORK Marche pas

In this last case, the real name "DOESN'T-WORK" is conserved as HTML class,
but translated to "DOESN_T_WORK" in the heading.

No problem in LaTeX.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Can't use char ">" in TODO state

[Bastien]

Hi Sébastien,

"Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> writes:

> I find this behavior not entirely satisfying, even if I can fully accept that
> ">" is a forbidden character in the TODO states. For example, we could think
> of a warning being generated, or of the state being fully ignored, or ...

I agree there is inconsistency here.  Special chars are allowed in TODO
keywords but they create the confusion you describe when used at the beg
or the end of the keyword ("NE>W" is safe AFAICT.)

> BTW, do you have an alternative for this "NEW" state, in 4 positions?
> ;-)

NIOU?

:)

-- 
 Bastien