emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Can't use char ">" in TODO state
Date: Wed, 26 Oct 2011 18:51:09 +0200	[thread overview]
Message-ID: <808vo7r91e.fsf@somewhere.org> (raw)
In-Reply-To: 80lisa3frm.fsf@somewhere.org

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

* 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,

Sebastien Vauban

  reply	other threads:[~2011-10-26 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 10:32 Can't use char ">" in TODO state Sebastien Vauban
2011-10-18 11:25 ` Michael Brand
2011-10-21 15:11   ` Bastien
2011-10-23  7:38     ` Nicolas Goaziou
2011-10-23 15:07       ` Jambunathan K
2011-10-23 16:19         ` Nicolas Goaziou
2011-10-23 18:07       ` Bastien
2011-10-24  9:22       ` Sebastien Vauban
2011-10-26 16:51         ` Sebastien Vauban [this message]
2011-10-21 15:07 ` Bastien

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:

  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=808vo7r91e.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* 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


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).