From: Dan Davison <email@example.com>
Subject: Re: html export with htmlized code blocks
Date: Tue, 19 May 2009 15:10:01 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <20090519181956.GD6662@mindcrime> (Dirk-Jan C. Binnema's message of "Tue, 19 May 2009 21:19:56 +0300")
"Dirk-Jan C. Binnema" <email@example.com> writes:
> Hi all,
> I sometimes use blocks of code in my org-files; currently, to make them
> look nice, I put the code in a buffer with their major mode (e.g, a blog
> perl in a buffer with perl-mode), then convert it to html with htmlize,
> and copy the result html back in an org-mode html block.
> I seems that I should be able to automate that a bit... ie., maybe
> something like:
> print "hello, world!";
> And *somehow* make that execute the steps I mentioned, and get something
> like; so I'd need to cut-out only the stuff within <pre></pre> the
> htmlize-generated html (it generates top-level html stuff which we
> should ignore I guess).
> <span class="cperl-nonoverridable">print</span> <span class="string">"hello, world!\n"</span>;</pre>
> But I'm not really sure if that would be the best approach. Did anyone
> do something like this before?
I think what you are describing is achieved by
* some heading
print "hello, world!";
Then you just export the buffer as HTML.
Sorry if I've misunderstood.
> Any tips?
next prev parent reply other threads:[~2009-05-19 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 18:19 html export with htmlized code blocks Dirk-Jan C. Binnema
2009-05-19 19:10 ` Dan Davison [this message]
2009-05-19 20:04 ` html export with htmlized code blocks [SOLVED] Dirk-Jan C. Binnema
2009-05-19 20:07 ` Dirk-Jan C. Binnema
2009-05-25 18:04 ` html export with htmlized code blocks [SOLVED, but...] Dirk-Jan C. Binnema
2009-05-25 18:33 ` Sebastian Rose
2009-05-25 18:35 ` Sebastian Rose
2009-05-25 20:03 ` Sebastian Rose
2009-05-19 20:20 ` html export with htmlized code blocks Sebastian Rose
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 \
* 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).