emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Matt Lundin <mdl@imapmail.org>
Cc: nicholas.dokos@hp.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Section between #+latex: declarations not converted during export
Date: Sun, 13 Mar 2011 15:59:57 -0400	[thread overview]
Message-ID: <16171.1300046397@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Matt Lundin <mdl@imapmail.org> of "Sun, 13 Mar 2011 09:31:48 EDT." <87r5abi1tn.fsf@fastmail.fm>

Matt Lundin <mdl@imapmail.org> wrote:

> In the following example...
> 
> * Testing
> #+latex: \custommacro{%
> [[http:www.google.com][Google]]
> /The quick brown fox./
> #+latex: }
> 
> ...the lines between the latex declarations are not exported:
> 
> \section{Testing}
> \label{sec-1}
> 
> \custommacro{%
> [[http:www.google.com][Google]]
> /The quick brown fox./
> }
> 
> I would expect this behavior with "#+begin_latex:...#+end_latex", but
> not with "#+latex".
> 

The opening brace in the `#+ latex:' line confuses something.
My usual workaround is to fake a closing brace in the comment:

--8<---------------cut here---------------start------------->8---
* Testing
#+latex: \custommacro{% fake it out }
[[http:www.google.com][Google]]
/The quick brown fox./
#+latex: }
--8<---------------cut here---------------end--------------->8---


which produces

--8<---------------cut here---------------start------------->8---
\section{Testing}
\label{sec-1}

\custommacro{% fake it out }
\href{http:www.google.com}{Google}
\emph{The quick brown fox.}
}
--8<---------------cut here---------------end--------------->8---

Nick

  reply	other threads:[~2011-03-13 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-13 13:31 Section between #+latex: declarations not converted during export Matt Lundin
2011-03-13 19:59 ` Nick Dokos [this message]
2011-03-14 12:56   ` Matt Lundin

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=16171.1300046397@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    /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).