From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Bach <phaebz@googlemail.com>
Subject: Re: problem with org-export-latex-todo-keyword-markup [7.4]
Date: Wed, 16 Feb 2011 17:22:41 +0200
Message-ID: <4D5BEBC1.2090402@googlemail.com>
References: <4D5B9A9A.3040306@googlemail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=47055 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PpjDv-0006mm-Dz
	for emacs-orgmode@gnu.org; Wed, 16 Feb 2011 10:23:24 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <phaebz@googlemail.com>) id 1PpjDu-0001ds-Es
	for emacs-orgmode@gnu.org; Wed, 16 Feb 2011 10:23:23 -0500
Received: from mail-ey0-f169.google.com ([209.85.215.169]:59699)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <phaebz@googlemail.com>) id 1PpjDu-0001dm-6N
	for emacs-orgmode@gnu.org; Wed, 16 Feb 2011 10:23:22 -0500
Received: by eyh6 with SMTP id 6so771298eyh.0
	for <emacs-orgmode@gnu.org>; Wed, 16 Feb 2011 07:23:21 -0800 (PST)
In-Reply-To: <4D5B9A9A.3040306@googlemail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: phaebz <phaebz@googlemail.com>
Cc: emacs-orgmode@gnu.org

On 02/16/2011 11:36 AM, phaebz wrote:
> I defined it as an associative list, as described in the manual:
> org-export-latex-todo-keyword-markup evaluates to (("new" . "\\new{%s}") ("done" . "\\done{%s}") ("todo" . "\\todo{%s}"))
>
> In my LaTeX header are the options:
> #+LATEX_HEADER: \def\todo#1{{\color{red}#1}}
> #+LATEX_HEADER: \def\done#1{{\color{green}#1}}
> #+LATEX_HEADER: \def\new#1{{\color{blue}#1}}
>
> Now I noticed that, in the exported pdf, all todo keywords are typeset in the same color, which is always the value of the first element in the a-list. In the above example, all keywords get set to blue, i.e. the LaTeX file contains odd things like \new{TODO}.
>
> According to the manual, I expect this behaviour - using the value of the first element - only for todo keywords for which there is no key in the a-list defined.
>
> Am I doing something wrong?

Actually, I am thinking of setting up a virtual mailing-list just for me, so that I can send my email there, since there seems to be a correlation between me sending my problems to this list and finding the solution on my own.

For completeness, obviously the keys have all to be upper case, i.e. (("NEW" . "\\new{%s}") ("DONE" . "\\done{%s}") ("TODO" . "\\todo{%s}")).

I will try to avoid these mails in the future.

Michael Bach