From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: Giulio Fella <g.fella@lineone.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Escaping braces and org-export-latex-classes behaviour
Date: Sat, 17 Apr 2010 22:09:30 +0200 [thread overview]
Message-ID: <q2y45c323461004171309i2ffb1956s12da7b07341d7da9@mail.gmail.com> (raw)
In-Reply-To: <w2veb666b081004161019g57ca115gb3eac2d1b505c0bc@mail.gmail.com>
I think the correct would be using Latex syntax like \color{red}{whatever}.
If you write using plain Tex syntax like {\color{red}whatever} org
will not understand that the outer curly brackets are part of the
command.
-- Darlan
2010/4/16 Giulio Fella <g.fella@lineone.net>:
> Hi,
>
> I have just upgraded from 6.33trans to 6.35g-55-g36d3e hoping to solve
> a problem with escaping braces.
>
> With LaTex_CLASS: beamer
>
> Something like
> {\color{red}whatever}
>
> exports to latex with escaped outer braces. Namely
>
> \{\color{red}whatever\}
>
> This is the same behaviour as in 6.33trans. I had read it was a bug
> which had been corrected. Is this a reappearing bug or is there a way
> round it?
>
> Also in version 6.33 the relevant content of org-export-latex-classes
> used to be exported before that of BEAMER_HEADER_EXTRA. Now it is
> parsed after it. Is there any variable I can set to reestablish the
> old behaviour?
>
> Many thanks in advance.
>
> Best wishes
> Giulio
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
next prev parent reply other threads:[~2010-04-17 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 17:19 Escaping braces and org-export-latex-classes behaviour Giulio Fella
2010-04-17 20:09 ` Darlan Cavalcante Moreira [this message]
2010-04-17 22:30 ` Giulio Fella
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=q2y45c323461004171309i2ffb1956s12da7b07341d7da9@mail.gmail.com \
--to=darcamo@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=g.fella@lineone.net \
/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).