emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: escaping of #+TEXT lines: \vspace vs \vspace*
Date: Wed, 23 Mar 2011 12:07:04 +0800	[thread overview]
Message-ID: <87lj06fpjr.fsf@ericabrahamsen.net> (raw)


In a certain org file I put this line into the export options:

#+begin_src org-mode
#+TEXT: \vspace*{0.5in}

The starred version is necessary, obviously, since this comes before any
text, and LaTeX will ignore a plain old \vspace{} in those cases.

This currently gets escaped as \vspace*\{0.5in\}, which keeps it from
working. I noticed that regular \vspace{} is not escaped, so I went
looking in org-latex.el, but can't begin to figure out which regexp in
which function is protecting the unstarred version, but not the starred

Is this fixable?


             reply	other threads:[~2011-03-23  4:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  4:07 Eric Abrahamsen [this message]
2011-03-23  9:00 ` escaping of #+TEXT lines: \vspace vs \vspace* Eric S Fraga
2011-03-23 10:28   ` [PATCH] Protect starred commands in LaTeX export correctly Lawrence Mitchell
2011-03-23 11:28     ` Eric Abrahamsen
2011-03-23 14:05     ` [Accepted] " Bastien Guerry
2011-03-23 14:11     ` [PATCH] " Eric S Fraga
2011-03-23 14:16     ` Bastien

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=87lj06fpjr.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).