org-latex-custom-lang-environments

org-latex-custom-lang-environments

[Jacob Gerlach]

[-- Attachment #1: Type: text/plain, Size: 712 bytes --]

Hello,

I thought I had successfully used this variable, but after restarting
emacs, I can no longer reproduce the documented behavior.

Given the following org file:
----------
#+BEGIN_SRC sh :exports code
echo "Hello"
#+END_SRC

# Local Variables:
# org-latex-listings: t
# org-latex-custom-lang-environments: (quote ((sh "myverbatim")))
# END:
----------

I expect to export
----------
\begin{myverbatim}
echo "Hello"
\end{myverbatim}
----------
(and I thought I had observed this behavior the first time I tried it).
Instead, I get
----------
\lstset{language=sh,label= ,caption= ,captionpos=b,numbers=none}
\begin{lstlisting}
echo "Hello"
\end{lstlisting}
----------

Am I missing something?

Regards,
Jake

[-- Attachment #2: Type: text/html, Size: 1164 bytes --]

Re: org-latex-custom-lang-environments

[Rasmus]

Hi Jake,

Jacob Gerlach <jacobgerlach@gmail.com> writes:

> I thought I had successfully used this variable, but after restarting
> emacs, I can no longer reproduce the documented behavior.
>
> Given the following org file:
> ----------
> #+BEGIN_SRC sh :exports code
> echo "Hello"
> #+END_SRC
>
> # Local Variables:
> # org-latex-listings: t
> # org-latex-custom-lang-environments: (quote ((sh "myverbatim")))
> # END:
> ----------

If I explicitly eval: 

    (org-babel-do-load-languages 'org-babel-load-languages '((sh . t)))
    (setq org-latex-custom-lang-environments '((sh "myverbatim"))
          org-latex-listings t)

And export

#+BEGIN_SRC sh :exports code
echo "Hello"
#+END_SRC

I get the the block wrapped in the desired environment.  I don't know why
your local variables are ignored, but it seems the result is the same when
using the Org-specific BIND keyword...

Rasmus




-- 
And I faced endless streams of vendor-approved Ikea furniture. . .

Re: org-latex-custom-lang-environments

[Jacob Gerlach]

Hello,

On Tue, May 19, 2015 at 11:29 AM, Rasmus <rasmus@gmx.us> wrote:
> If I explicitly eval:
>
>     (org-babel-do-load-languages 'org-babel-load-languages '((sh . t)))
>     (setq org-latex-custom-lang-environments '((sh "myverbatim"))
>           org-latex-listings t)
>
> And export
>
> #+BEGIN_SRC sh :exports code
> echo "Hello"
> #+END_SRC
>
> I get the the block wrapped in the desired environment.  I don't know why
> your local variables are ignored, but it seems the result is the same when
> using the Org-specific BIND keyword...


Yes, I see the same - setting them with setq gives the desired
behavior. I must have done this during my initial experimentation
which is why it worked until I restarted emacs.

I know the local variables are parsed - I get asked for confirmation
on potentially unsafe values, and after confirming, C-h v ... shows
that the value has been set correctly.

Does this maybe have to do with export happening in a temporary
buffer? I would assume that file local variables get copied over to
the temp buffer as buffer local variables. Is that the case?

Regards,
Jake

Re: org-latex-custom-lang-environments

[Rasmus]

Jacob Gerlach <jacobgerlach@gmail.com> writes:

> Hello,
>
> On Tue, May 19, 2015 at 11:29 AM, Rasmus <rasmus@gmx.us> wrote:
>> If I explicitly eval:
>>
>>     (org-babel-do-load-languages 'org-babel-load-languages '((sh . t)))
>>     (setq org-latex-custom-lang-environments '((sh "myverbatim"))
>>           org-latex-listings t)
>>
>> And export
>>
>> #+BEGIN_SRC sh :exports code
>> echo "Hello"
>> #+END_SRC
>>
>> I get the the block wrapped in the desired environment.  I don't know why
>> your local variables are ignored, but it seems the result is the same when
>> using the Org-specific BIND keyword...
>
>
> Yes, I see the same - setting them with setq gives the desired
> behavior. I must have done this during my initial experimentation
> which is why it worked until I restarted emacs.
>
> I know the local variables are parsed - I get asked for confirmation
> on potentially unsafe values, and after confirming, C-h v ... shows
> that the value has been set correctly.
>
> Does this maybe have to do with export happening in a temporary
> buffer? I would assume that file local variables get copied over to
> the temp buffer as buffer local variables. Is that the case?

No.  And actually it works, only it shouldn't be quoted.

# -*- org-export-allow-bind-keywords: t; -*-
#+BIND: org-latex-listings t
#+BIND: org-latex-custom-lang-environments ((sh "myverbatim"))

#+BEGIN_SRC sh :exports code
echo "Hello"
#+END_SRC


Or

#+BEGIN_SRC sh :exports code
echo "Hello"
#+END_SRC

# Local Variables:
# org-latex-listings: t
# org-latex-custom-lang-environments:  ((sh "myverbatim"))
# END:


Hope it helps,
Rasmus

-- 
Don't panic!!!