From: "Marvin ‘quintus’ Gülker" <post+orgmodeml@guelker.eu>
To: emacs-orgmode@gnu.org
Subject: Re: Differentiate source blocks in export?
Date: Tue, 24 Nov 2020 17:07:27 +0100 [thread overview]
Message-ID: <87sg8yivr4.fsf@guelker.eu> (raw)
In-Reply-To: <87a6v7gdej.fsf@fastmail.fm> (Joost Kremers's message of "Tue, 24 Nov 2020 13:14:28 +0100")
Hi!
Am Dienstag, dem 24. November 2020 schrieb Joost Kremers:
> 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.
You can use the BEGIN_EXPORT/END_EXPORT pair to include a literal HTML
DIV tag around your target code block. Try this:
Wrapped code block in a div with a custom class:
#+BEGIN_EXPORT html
<div class="myclass">
#+END_EXPORT
#+BEGIN_SRC c
#include <stdio.h>
int main(int argc, char* argv[])
{
printf("This is wrapped in the div\n");
return 0;
}
#+END_SRC
#+BEGIN_EXPORT html
</div>
#+END_EXPORT
Normal codeblock without:
#+BEGIN_SRC c
#include <stdio.h>
int main(int argc, char* argv[])
{
printf("This is not wrapped in anything unusual\n");
return 0;
}
#+END_SRC
Note how one of the EXPORT blocks wraps the opening tag of the DIV and
the other one wraps the closing tag.
-quintus
--
Dipl.-Jur. M. Gülker | https://mg.guelker.eu | For security:
Passau, Germany | kontakt@guelker.eu | () Avoid HTML e-mail
European Union | PGP: see homepage | /\ http://asciiribbon.org
next prev parent reply other threads:[~2020-11-24 16:08 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
2020-11-24 16:07 ` Marvin ‘quintus’ Gülker [this message]
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=87sg8yivr4.fsf@guelker.eu \
--to=post+orgmodeml@guelker.eu \
--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).