emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Simon Brown <simon@cliffestones.demon.co.uk>
To: Rares Pop <rares.pop@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: export TODO keyword
Date: Mon, 16 Aug 2010 14:14:39 +0100	[thread overview]
Message-ID: <87r5hyhf7k.wl%simon@cliffestones.demon.co.uk> (raw)
In-Reply-To: <AANLkTimyY3jOc4wz2P-5Fb8-oJ7rYCZHuyp1FQyfr8yK@mail.gmail.com>

Hi Rares,

At Mon, 16 Aug 2010 14:27:47 +0300,
Rares Pop <rares.pop@gmail.com> wrote:
> I've found part of the problem but I don't know the cause.
> The *.tex file was generated with curly brackets
> (e.g. \section{\textbf\{TODO\} Task 1}) - i've attached the *.tex file
> And if I remove the slashes(*\ \)* signs the latex code will be something
> like this (e.g \section{\textbf{TODO} Task 1})
> and by exporting it to PDF it looks ok.
> 
> The value of the variable *Org Export Latex Todo Keyword Markup* is *
> \textbf{%s}*
> *
> *
> So it seems that somewhere on the road some slash signs are added without
> permission.

This sounds like a bug I encountered a while back:
http://article.gmane.org/gmane.emacs.orgmode/24900

Carsten fixed it a while ago (Thanks!)

I suggest you update.

Simon

  reply	other threads:[~2010-08-16 13:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16  8:39 export TODO keyword Rares Pop
2010-08-16  8:45 ` Carsten Dominik
2010-08-16  9:06   ` Rares Pop
2010-08-16 10:36     ` Carsten Dominik
2010-08-16 11:27       ` Rares Pop
2010-08-16 13:14         ` Simon Brown [this message]
2010-08-16 13:24           ` Rares Pop
2010-08-16 14:08         ` Sebastian Rose
2010-08-16 15:10           ` Rares Pop
2010-08-16 15:37             ` Nick Dokos
2010-08-16 15:42               ` Carsten Dominik
2010-08-16 15:49                 ` Puneeth
2010-08-16 15:59                   ` Carsten Dominik
2010-08-16 12:12     ` Noorul Islam K M

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87r5hyhf7k.wl%simon@cliffestones.demon.co.uk \
    --to=simon@cliffestones.demon.co.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=rares.pop@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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