emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: A question/bug report(?)
Date: Wed, 30 Mar 2022 14:05:22 +0700	[thread overview]
Message-ID: <t20vfk$mt4$1@ciao.gmane.io> (raw)
In-Reply-To: <CAO48Bk_dJs1=5zgpcZwODaTsRqyRsKq1ALj6WpaXCc4bDjW3FQ@mail.gmail.com>

On 30/03/2022 12:14, Pedro Andres Aranda Gutierrez wrote:
> 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

I think, it is better to add :attributes parameter support to 
#+begin_example block. It may be added to org, for a while you can use a 
custom derived backend. See info "(org) Advanced Export Configuration" 

You need to define an example-block filter, current implementation is 

I never tried it but perhaps it is possible to customize the listings 
LaTeX package for automatic highlighting of text after shell prompt. In 
Org #+begin_src blocks may use lstlisting environment.

      reply	other threads:[~2022-03-30  7:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26  7:58 Pedro Andres Aranda Gutierrez
2022-03-29 13:12 ` Eric S Fraga
2022-03-29 14:44   ` Max Nikulin
2022-03-29 15:04     ` Eric S Fraga
2022-03-30  5:14   ` Pedro Andres Aranda Gutierrez
2022-03-30  7:05     ` Max Nikulin [this message]

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:

  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='t20vfk$mt4$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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