emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: LaTeX fragments to deal with character {
Date: Sat, 13 Dec 2014 22:51:52 +0100	[thread overview]
Message-ID: <87y4qb8bgn.fsf@gmx.us> (raw)
In-Reply-To: CAOnPmeU29_a1iTEwNBqsSzrB3s30_z45PabFUk69UJreV4Utkw@mail.gmail.com

Hi Kevin,

> Org-mode version 6.33x

O-o-okay.  The current stable version is 8.2 and the export framework
changed in v8.  If possible, you should upgrade.

"kevin.lemorzadec" <kevin.lemorzadec@mun.ca> writes:

> I am trying to do a latex loop in org mode. When I use the latex syntax
> directly, the character "{" are exported as"\{" as in case 1 below. If I
> use ‘\(...\)’ it does keep the "{" characters but the ‘\(...\)' stays in
> the .tex created (case 2 below) giving me an error when I try to generate
> the pdf.
> Is there an other was to export the "{" characters?

I don't remember if this works in Org6 and it's not available to me.


#+LATEX: loop line 1
#+LATEX: loop line 2
#+LATEX: loop line 3


My loop {}

Let's hope one of those works in Org6.


Vote for proprietary math!

      reply	other threads:[~2014-12-13 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 21:28 LaTeX fragments to deal with character { kevin.lemorzadec
2014-12-13 21:51 ` Rasmus [this message]

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=87y4qb8bgn.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.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).