emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: escaping of #+TEXT lines: \vspace vs \vspace*
Date: Wed, 23 Mar 2011 09:00:17 +0000	[thread overview]
Message-ID: <87mxkmp5y6.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87lj06fpjr.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 23 Mar 2011 12:07:04 +0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Hi,
> In a certain org file I put this line into the export options:
> #+begin_src org-mode
> #+TEXT: \vspace*{0.5in}
> #+end_src

Should this not be 

#+LATEX: \vspace*{0.5in}

instead of TEXT?

By the way, if you want such commands to be recognised inline within
normal org text, without having to escape them, I do the following:

#+latex_header: \newcommand{\Gap}[1]{\vspace*{#1}}

and then simply type \Gap{0.5in} whenever you want to invoke this vspace
command.  One could argue that the latex escaping that org does should
include *'ed commands as well... but this may have other repercussions
that I am not aware of.

: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs
: using Org-mode version 7.5 (release_7.5.97.g078c0)

  reply	other threads:[~2011-03-23  9:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  4:07 escaping of #+TEXT lines: \vspace vs \vspace* Eric Abrahamsen
2011-03-23  9:00 ` Eric S Fraga [this message]
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=87mxkmp5y6.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \


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