From: Bruno Barbier <brubar.cs@gmail.com>
To: Detlev Zundel <dzu@member.fsf.org>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Problems with :exports results for shell and plantuml code [9.6-pre (release_9.5.5-995-g4b9aef @ /home/dzu/.emacs.d/straight/build/org-mode/)]
Date: Sat, 11 Feb 2023 09:11:56 +0100 [thread overview]
Message-ID: <63e74dce.050a0220.f428.f3c1@mx.google.com> (raw)
In-Reply-To: <87fsbecy5w.fsf@member.fsf.org>
Detlev Zundel <dzu@member.fsf.org> writes:
> Hi orgmode-list!
>
> I currently have a problem while exporting org-babel blocks to html or
> latex output. Even though I explicitely specify ':exports result' for
> the blocks, the exported document contains both the (syntax colored)
> code block and the code. I noticed this in a plantuml block that I use
> to generate inline diagrams. Exporting to PDF actually yields a PDF
> looking like it contains only the results, but there are errors in the
> '*Org PDF LaTeX Outupt*' buffer, saying that pygmentize misses a lexer
> for plantuml. Checking the generated LaTeX code indeed shows that the
> code is exported to LaTeX, even though ':exports result' is passed as a
> header argument.
Maybe:
:exports result
=>
:exports results
?
Bruno
next prev parent reply other threads:[~2023-02-11 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 21:43 [BUG] Problems with :exports results for shell and plantuml code [9.6-pre (release_9.5.5-995-g4b9aef @ /home/dzu/.emacs.d/straight/build/org-mode/)] Detlev Zundel
2023-02-11 8:11 ` Bruno Barbier [this message]
2023-02-11 18:32 ` Detlev Zundel
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=63e74dce.050a0220.f428.f3c1@mx.google.com \
--to=brubar.cs@gmail.com \
--cc=dzu@member.fsf.org \
--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).