Re: [O] Can't use char ">" in TODO state
Hi Nicolas and Bastien, > Nicolas Goaziou wrote: >> Bastien writes: >>> Michael Brand 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: [O] Can't use char ">" in TODO state
Hi Nicolas, Nicolas Goaziou wrote: > Bastien writes: >> Michael Brand 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: [O] Can't use char ">" in TODO state
Nicolas Goaziou 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: [O] Can't use char ">" in TODO state
Jambunathan K 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: [O] Can't use char ">" in TODO state
Hello, Bastien writes: > Michael Brand 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: [O] Can't use char ">" in TODO state
Hi, Michael Brand 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: [O] Can't use char ">" in TODO state
Hi Sébastien,
"Sebastien Vauban" 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
Re: [O] Can't use char ">" in TODO state
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
[O] Can't use char ">" in TODO state
#+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
