emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Charles Berry <ccberry@ucsd.edu>
To: emacs-orgmode@gnu.org
Subject: Re: [new exporter] latex: why does {{}} become \{\{\}\} ?
Date: Sun, 21 Oct 2012 18:47:04 +0000 (UTC)	[thread overview]
Message-ID: <loom.20121021T204152-63@post.gmane.org> (raw)
In-Reply-To: 80ipa6vcgw.fsf@somewhere.org

Sebastien Vauban <wxhgmqzgwmuf@...> writes:

> 
> Hi Nicolas,
> 
> Nicolas Goaziou wrote:
> > "Sebastien Vauban"
> >> Within a LaTeX block (#+begin_latex) or within a Babel block for LaTeX
> >> language (#+begin_src latex)?  Do you make a difference?
> >
> > There's a big difference.
> >
> > #+begin_latex means "paste this code unmodified in the latex back-end,
> > and only in the latex back-end". Nothing is evaluated.

I guess I do not understand.

Using git pull today,

(org-export-to-buffer 'e-latex "scratch.tex") exports this


#+begin_latex
  \begin{displaymath}
    \mbox{a}=\frac{b}{1 + c}
  \end{displaymath}
#+end_latex 

 
as this

\begin{latex}
\begin{displaymath}
  \mbox{a}=\frac{b}{1 + c}
\end{displaymath}
\end{latex}

So how do I get rid of the enclosing lines:

\begin{latex} 
\end{latex} 

??

Chuck

> >
> > With a #+begin_src latex block, depending on :exports parameter, you can
> > produce something (in this case, probably an image file) and create
> > a link valid in any back-end, as long as it supports the file format.
> >
> > Both are possible.
> 
> I realize having taken the bad habit of only using #+begin_src latex blocks
> even for code that only matters for the LaTeX back-end (such as TikZ
> decorations). By carefully using the Babel options, it comes down to the same
> effect/behavior, but, OK, that's NOT the Right Way To Do!
> 
> Best regards,
>   Seb
> 

next prev parent reply	other threads:[~2012-10-21 18:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 15:29 [new exporter] latex: why does {{}} become \{\{\}\} ? Myles English
2012-10-16 19:21 ` Nicolas Goaziou
2012-10-16 21:26   ` Myles English
2012-10-16 21:35   ` Sebastien Vauban
2012-10-17 12:03     ` Nicolas Goaziou
2012-10-19 13:05       ` Sebastien Vauban
2012-10-21 18:47         ` Charles Berry [this message]
2012-10-21 19:14           ` cberry
2012-10-21 19:51             ` Myles English

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=loom.20121021T204152-63@post.gmane.org \
    --to=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.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

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