emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Protect starred commands in LaTeX export correctly
Date: Wed, 23 Mar 2011 19:28:57 +0800	[thread overview]
Message-ID: <87hbaudqiu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: m3zkom15w6.fsf_-_@e4300lm.epcc.ed.ac.uk

Lawrence Mitchell <wence@gmx.li> writes:

> * lisp/org-latex.el (org-export-latex-preprocess): Correctly
> match starred command names.
> Many LaTeX commands exist in both normal and starred forms.  Adjust
> the regexp in `org-export-latex-preprocess' to match the starred form
> as well.

Awesome! This seems like a good idea. Though the other Eric's suggestion
just to use #+LATEX of course worked perfectly, I'm not sure why I
thought I needed #+TEXT in order to place the text before the first


  reply	other threads:[~2011-03-23 11:29 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
2011-03-23 10:28   ` [PATCH] Protect starred commands in LaTeX export correctly Lawrence Mitchell
2011-03-23 11:28     ` Eric Abrahamsen [this message]
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=87hbaudqiu.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).