[new exporter] latex: why does {{}} become \{\{\}\} ?

[new exporter] latex: why does {{}} become \{\{\}\} ?

[Myles English]

Hi,

Org-mode version 7.9.2 (release_7.9.2-441-gf287ab @ /home/myles/.emacs.d/plugins/org-mode/lisp/)

Can anyone tell me please why (in the examples below) {} exports fine
but {{}} exports as \{\{\}\} ?  Am I meant to wrap these in
#+begin_latex blocks?

In my .org file:

\tikzset{help lines/.style=very thin}
\tikzset{help grid/.style={help lines,color=blue!50}}

In the resulting .tex file

\tikzset{help lines/.style=very thin}
\tikzset\{help grid/.style=\{help lines,color=blue!50\}\}

Thanks,

Myles

Re: [new exporter] latex: why does {{}} become \{\{\}\} ?

[Nicolas Goaziou]

Hello,

"Myles English" <mylesenglish@gmail.com> writes:

> Can anyone tell me please why (in the examples below) {} exports fine
> but {{}} exports as \{\{\}\} ?  Am I meant to wrap these in
> #+begin_latex blocks?

You're writing LaTeX code in an Org buffer. This is only possible to
a limited extent. In particular, these lines should indeed go within
a LaTeX block. Otherwise, they will be protected to appear as-is in the
output.


Regards,

-- 
Nicolas Goaziou

Re: [new exporter] latex: why does {{}} become \{\{\}\} ?

[Myles English]

Nicolas Goaziou writes:

> You're writing LaTeX code in an Org buffer. This is only possible to
> a limited extent. In particular, these lines should indeed go within
> a LaTeX block. Otherwise, they will be protected to appear as-is in the
> output.

Thanks, just confirming that was helpful, me and my emacs were confused
somehow and #+begin_latex was coming out as \begin{latex}, it may have
been a missing bracket.

Myles

Re: [new exporter] latex: why does {{}} become \{\{\}\} ?

[Sebastien Vauban]

Hello Nicolas,

Nicolas Goaziou wrote:
> "Myles English" <mylesenglish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
>> Can anyone tell me please why (in the examples below) {} exports fine
>> but {{}} exports as \{\{\}\} ?  Am I meant to wrap these in
>> #+begin_latex blocks?
>
> You're writing LaTeX code in an Org buffer. This is only possible to
> a limited extent. In particular, these lines should indeed go within
> a LaTeX block.

Within a LaTeX block (#+begin_latex) or within a Babel block for LaTeX
language (#+begin_src latex)?  Do you make a difference?

Best regards,
Seb

-- 
Sebastien Vauban

Re: [new exporter] latex: why does {{}} become \{\{\}\} ?

[Nicolas Goaziou]

Hello,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> Hello Nicolas,
>
> Nicolas Goaziou wrote:
>> "Myles English" <mylesenglish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> Can anyone tell me please why (in the examples below) {} exports fine
>>> but {{}} exports as \{\{\}\} ?  Am I meant to wrap these in
>>> #+begin_latex blocks?
>>
>> You're writing LaTeX code in an Org buffer. This is only possible to
>> a limited extent. In particular, these lines should indeed go within
>> a LaTeX block.
>
> 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.

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.


Regards,

-- 
Nicolas Goaziou

Re: [new exporter] latex: why does {{}} become \{\{\}\} ?

[Sebastien Vauban]

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

-- 
Sebastien Vauban

Re: [new exporter] latex: why does {{}} become \{\{\}\} ?

[Charles Berry]

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
> 

Re: [new exporter] latex: why does {{}} become \{\{\}\} ?

[cberry]

Charles Berry <ccberry@ucsd.edu> writes:


NEVER MIND.

I just restarted my emacs and the export went as it should without the
offending

\begin{latex}
\end{latex}

lines.

Likely someting weird in my setup caused this.

Sorry for the noise.

Chuck

> 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

Re: [new exporter] latex: why does {{}} become \{\{\}\} ?

[Myles English]

cberry@tajo.ucsd.edu writes:

> Charles Berry <ccberry@ucsd.edu> writes:
>
>
> NEVER MIND.
>
> I just restarted my emacs and the export went as it should without the
> offending
>
> \begin{latex}
> \end{latex}
>
> lines.
>
> Likely someting weird in my setup caused this.

That happend to me too but I don't know what caused it.

Myles