Re: A question/bug report(?)

[Pedro Andres Aranda Gutierrez]

Hi Eric,

Thanks for answering :-) I'm currently solving the issue with

#+BEGIN_export LaTeX
\begin{verbatim}[commandchars=\\\{\}]
student@juju:~$ \textbf{sudo bootstrap-juju.sh}
\end{verbatim}
#+END_export

What I was wondering is whether we could have something like:

#+ATTR_LATEX :raw t :attributes [commandchars=\\\{\}]

#+BEGIN_verbatim
student@juju:~$ \textbf{sudo bootstrap-juju.sh}
#+END_verbatim

With that ":raw t" the text between the BEGIN_ and END_ would not go through the protecttexttt function. (of course, without the :raw t everything would work as today).

Again, it's just because it would be a cleaner to read. I have an yasnippet in place, so it wouldn't actually mean more or less typing.

Best, /PA

On Tue, 29 Mar 2022 at 15:12, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:

I'm not sure but maybe you want to use a src block,

#+begin_src latex :exports results
...
#+end_src

?  I am not entirely clear how you wish org to know what is "raw" and
what is "LaTeX".

--
: Eric S Fraga, with org release_9.5.2-420-g971eb6 in Emacs 29.0.50

--

Fragen sind nicht da um beantwortet zu werden,

Fragen sind da um gestellt zu werden

Georg Kreisler

Headaches with a Juju log:

unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet