unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* org-export-latex-verbatim-wrap error
@ 2015-11-18 14:35 Dushyant Juneja
  2015-11-18 16:51 ` Rasmus
  2015-11-19  6:57 ` Dushyant Juneja
  0 siblings, 2 replies; 4+ messages in thread
From: Dushyant Juneja @ 2015-11-18 14:35 UTC (permalink / raw)
  To: help-gnu-emacs@gnu.org

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

Hi,

The above variable seems to have no effect on verbatim environments in org
mode 8.2.10. I tried Eric Schlute's example:
##############################
** simple latex verbatim wrap example
   :PROPERTIES:
   :DATE:     2011-05-05
   :END:
#+begin_src emacs-lisp :results silent
  (setq org-export-latex-verbatim-wrap
        '("{\\scriptsize\n\\begin{verbatim}\n" . "\\end{verbatim}\n}\n"))
#+end_src

#+begin_src sh
  echo eric schulte
  echo another
#+end_src
################################

This, however, renders as in the pic below for me. Any hints/help would be
greatly appreciated - I am looking for using this in a report.

Dushyant
[image: pasted1]

[-- Attachment #2: pasted1 --]
[-- Type: image/png, Size: 15843 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: org-export-latex-verbatim-wrap error
  2015-11-18 14:35 org-export-latex-verbatim-wrap error Dushyant Juneja
@ 2015-11-18 16:51 ` Rasmus
  2015-11-19  6:57 ` Dushyant Juneja
  1 sibling, 0 replies; 4+ messages in thread
From: Rasmus @ 2015-11-18 16:51 UTC (permalink / raw)
  To: help-gnu-emacs

Hi,

Dushyant Juneja <juneja.dushyant@gmail.com> writes:

> #+begin_src emacs-lisp :results silent
>   (setq org-export-latex-verbatim-wrap
>         '("{\\scriptsize\n\\begin{verbatim}\n" . "\\end{verbatim}\n}\n"))
> #+end_src

This variable doesn't exist since the switch to the ox export engine.

For LaTeX exports, you can format src blocks using verbatim, minted or the
listings package.  See the docstring of org-latex-listings.

For specific languages you can specify custom export environments.  See
the docstring of org-latex-custom-lang-environments.

Hope it helps,
Rasmus

-- 
The right to be left alone is a human right




^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: org-export-latex-verbatim-wrap error
  2015-11-18 14:35 org-export-latex-verbatim-wrap error Dushyant Juneja
  2015-11-18 16:51 ` Rasmus
@ 2015-11-19  6:57 ` Dushyant Juneja
  2015-11-19 11:21   ` Rasmus
  1 sibling, 1 reply; 4+ messages in thread
From: Dushyant Juneja @ 2015-11-19  6:57 UTC (permalink / raw)
  To: help-gnu-emacs@gnu.org

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

Hi Rasmus,

Somehow, the replies never seem to reach my inbox. Some stubborn filter, I
guess.

> This variable doesn't exist since the switch to the ox export engine.

Thanks for the information on this one.

> For LaTeX exports, you can format src blocks using verbatim, minted or
the
> listings package.  See the docstring of org-latex-listings.

I could use listings for my application. However, there are a few issues:
1. (setq org-latex-listings 'listings) seems to take care only for src
blocks, not example blocks. The text between #+begin_example..#+end_example
is still exported to verbatim.

2. I am looking to 'frame' my lists, and possibly pass more options to the
listing environment. Is there a possibility to do this?

Please suggest a way out.

Dushyant


On Wed, Nov 18, 2015 at 8:05 PM Dushyant Juneja <juneja.dushyant@gmail.com>
wrote:

> Hi,
>
> The above variable seems to have no effect on verbatim environments in org
> mode 8.2.10. I tried Eric Schlute's example:
> ##############################
> ** simple latex verbatim wrap example
>    :PROPERTIES:
>    :DATE:     2011-05-05
>    :END:
> #+begin_src emacs-lisp :results silent
>   (setq org-export-latex-verbatim-wrap
>         '("{\\scriptsize\n\\begin{verbatim}\n" . "\\end{verbatim}\n}\n"))
> #+end_src
>
> #+begin_src sh
>   echo eric schulte
>   echo another
> #+end_src
> ################################
>
> This, however, renders as in the pic below for me. Any hints/help would be
> greatly appreciated - I am looking for using this in a report.
>
> Dushyant
> [image: pasted1]
>

[-- Attachment #2: pasted1 --]
[-- Type: image/png, Size: 15843 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: org-export-latex-verbatim-wrap error
  2015-11-19  6:57 ` Dushyant Juneja
@ 2015-11-19 11:21   ` Rasmus
  0 siblings, 0 replies; 4+ messages in thread
From: Rasmus @ 2015-11-19 11:21 UTC (permalink / raw)
  To: help-gnu-emacs

Hi Dushyant,

Dushyant Juneja <juneja.dushyant@gmail.com> writes:

> Somehow, the replies never seem to reach my inbox. Some stubborn filter, I
> guess.

I may not have replied to your inbox.

> I could use listings for my application. However, there are a few issues:
> 1. (setq org-latex-listings 'listings) seems to take care only for src
> blocks, not example blocks. The text between #+begin_example..#+end_example
> is still exported to verbatim.

This is correct.  Perhaps listings has some pseudo language.  In any case,
you could use an export filter.  I think you might have to share a
concrete example to 

> 2. I am looking to 'frame' my lists, and possibly pass more options to the
> listing environment. Is there a possibility to do this?

Sure, check the docstrings of org-latex-listings-options and
org-latex-listings.  E.g. something like

    (add-to-list 'org-latex-packages-alist '("" "listings"))
    (add-to-list 'org-latex-packages-alist "\lstset{....}")

Hope it helps,
Rasmus

-- 
Vote for proprietary math!




^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-11-19 11:21 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-18 14:35 org-export-latex-verbatim-wrap error Dushyant Juneja
2015-11-18 16:51 ` Rasmus
2015-11-19  6:57 ` Dushyant Juneja
2015-11-19 11:21   ` Rasmus

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