[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Can't use char ">" in TODO state
From: |
Sebastien Vauban |
Subject: |
Re: [O] Can't use char ">" in TODO state |
Date: |
Wed, 26 Oct 2011 18:51:09 +0200 |
User-agent: |
Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (windows-nt) |
Hi Nicolas and Bastien,
> Nicolas Goaziou wrote:
>> Bastien <address@hidden> writes:
>>> Michael Brand <address@hidden> 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, Bastien, 2011/10/21