From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Differentiate source blocks in export?
Date: Tue, 24 Nov 2020 11:00:53 -0500 [thread overview]
Message-ID: <CAJ51ETpA2CEhPdYMY3dpEQRNB5kq5P73jC8pPScZwzNjLGB+PQ@mail.gmail.com> (raw)
In-Reply-To: <87a6v7gdej.fsf@fastmail.fm>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
I think you would have to use some kind of filter to look either for an
#+attr_html or src-header argument, and modify the html output for that.
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Tue, Nov 24, 2020 at 7:16 AM Joost Kremers <joostkremers@fastmail.fm>
wrote:
> Hi all,
>
> I was wondering if there's a way to distinguish between different kind of
> source
> code blocks when exporting to HTML.
>
> Specifically, I would like a way to mark certain code blocks in my Org
> file so
> that those code blocks get a specific class in the HTML export. I can then
> style
> them with some CSS to make them stand out visually. I know I can use
> special
> blocks to get divs with a custom class, but I don't want to lose all the
> benefits of code blocks...
>
> I tried Google and the Org manual but I haven't been able to find anything
> on
> this.
>
> TIA
>
> --
> Joost Kremers
> Life has its moments
>
>
[-- Attachment #2: Type: text/html, Size: 1738 bytes --]
next prev parent reply other threads:[~2020-11-24 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 12:14 Differentiate source blocks in export? Joost Kremers
2020-11-24 16:00 ` John Kitchin [this message]
2020-11-24 16:07 ` Marvin ‘quintus’ Gülker
2020-11-24 16:15 ` John Kitchin
2020-11-24 16:22 ` Diego Zamboni
2020-11-24 17:41 ` Eric S Fraga
2020-11-24 22:02 ` Joost Kremers
2020-11-25 8:02 ` Eric S Fraga
2020-11-25 8:37 ` Joost Kremers
2020-11-25 9:20 ` Eric S Fraga
2020-11-25 13:24 ` Font lock in inner blocks [was: Re: Differentiate source blocks in export?] Joost Kremers
2020-11-24 21:55 ` Differentiate source blocks in export? Joost Kremers
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=CAJ51ETpA2CEhPdYMY3dpEQRNB5kq5P73jC8pPScZwzNjLGB+PQ@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=joostkremers@fastmail.fm \
/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).