emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeff Trull <edaskel@att.net>
To: Jeff Trull <edaskel@att.net>, emacs-orgmode@gnu.org
Subject: Re: ATTR_LATEX :options ignored for source code
Date: Sun, 15 May 2016 23:25:21 -0700	[thread overview]
Message-ID: <CAF_DUeHBB=R0QfCNvvD2u6SrCcM5-QzhtP_+PH_SgRkzs5BDXg@mail.gmail.com> (raw)
In-Reply-To: <87lh3bwzav.fsf@saiph.selenimh>

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

Ah, I see...

I was expecting the "option to the environment" to look like:

\begin{lstlisting}[commentstyle=\bfseries]

Though doing it with \lstset will produce the same result if the option is
placed at the end, which it is.

Thanks for your help,
Jeff

On Sun, May 15, 2016 at 12:33 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Jeff Trull <edaskel@att.net> writes:
>
> > According to the manual users can supply #+ATTR_LATEX: :options ... prior
> > to a source section and the options present will be supplied to the
> > environment (lstlistings in my case).  I find that this does not work -
> > regardless of settings, no options are supplied to the lstlistings
> > environment.  Attached is a test case that demonstrates the problem.  It
> is
> > taken from the manual.
>
> FWIW, I cannot reproduce it. I get
>
>   \lstset{language=C++,label= ,caption=
> ,captionpos=b,numbers=none,commentstyle=\bfseries}
>   \begin{lstlisting}
>   using foo_t = int;
>   struct bar_t {
>       foo_t a;     // this comment should be bold
>   };
>   \end{lstlisting}
>
> What Org version are you using?
>
> Regards,
>
> --
> Nicolas Goaziou
>

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

      reply	other threads:[~2016-05-16  6:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-14 21:09 ATTR_LATEX :options ignored for source code Jeff Trull
2016-05-15  7:33 ` Nicolas Goaziou
2016-05-16  6:25   ` Jeff Trull [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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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='CAF_DUeHBB=R0QfCNvvD2u6SrCcM5-QzhtP_+PH_SgRkzs5BDXg@mail.gmail.com' \
    --to=edaskel@att.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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