emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Simon Brown <simon@cliffestones.demon.co.uk>
Cc: Org Mode List <Emacs-orgmode@gnu.org>
Subject: Re: Latex export colouring and properties
Date: Tue, 12 May 2009 13:45:18 +0200	[thread overview]
Message-ID: <03B6821B-DA54-4EAE-A20C-30390FD93CF8@gmail.com> (raw)
In-Reply-To: <20090507181704.GC14045@wilbury.neustadt.demon.co.uk>

On May 7, 2009, at 8:17 PM, Simon Brown wrote:

> * Carsten Dominik (carsten.dominik@gmail.com) wrote:
>> I guess this could be implemented, but for me, LaTeX is still mainly
>> used for B&W text, so it never occurred to me.  I guess we could wrap
>> some
>> kind of macro around it, and you would be responsible to define that
>> macro....
> I've thought about this some more and although I love colour
> everywhere what I'm after is actually quite simple. Firstly on
> reflection I agree exporting draws would be bad.
> 	   Where I work there are a lot of network restrictions which
> means many documents are exchanged in printed form. Highlighting the
> todo state red or green as it is within org-mode, makes important
> points obvious. Some sort of colouring for the date stamps for  
> scheduled,
> deadline and closed would be nice as well


I am not going to make this happen by default, but you can now  
configure things (with the latest git version:

In the Org file:

#+LATEX_HEADER: \usepackage{color}
#+LATEX_HEADER: \def\todo#1{{\color{red}#1}}
#+LATEX_HEADER: \def\done#1{{\color{green}#1}}

In .emacs

(setq org-export-latex-todo-keyword-markup '("\\todo{%s}" . "\ 

It is also possible to use different colors for each keyword.

See also the variables



- Carsten

  reply	other threads:[~2009-05-12 11:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 16:04 Latex export colouring and properties Simon Brown
2009-05-06 10:30 ` Carsten Dominik
2009-05-07 18:17   ` Simon Brown
2009-05-12 11:45     ` Carsten Dominik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-22 15:45 Simon Brown

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=03B6821B-DA54-4EAE-A20C-30390FD93CF8@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=simon@cliffestones.demon.co.uk \


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