From: "Dirk-Jan C. Binnema" <djcb.bulk@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: html export with htmlized code blocks [SOLVED, but...]
Date: Mon, 25 May 2009 21:04:36 +0300 [thread overview]
Message-ID: <20090525180436.GB6128@mindcrime> (raw)
In-Reply-To: <20090519200751.GF6662@mindcrime>
Dave already gave the excellent #+BEGIN_SRC tip and I have happily
included it in my workflow:
http://emacs-fu.blogspot.com/2009/05/writing-and-blogging-with-org-mode.html
One small remaining question...
he html for the code blocks looks something like:
<pre class="src src-emacs-lisp">
<span style="color: #666666;">;; </span><span style="color: #bbbbbb; font-style: italic;">some comment
So, the code has all of it's CSS inline -- which is nice because that
way people who read through aggregators or feed readers also get the
colors.
*however* the <pre class="src src-emacs-lisp"> expects to find its style
information in <head>. And that part is not used by RSS / aggregators --
I am using a dark color theme in my emacs, which is reflect in the
colors in use for code: the whole <pre> block should
have a black background, so people can read my light-yellow code...
So, either I'd like the <pre> to have the styles inline (like the rest
of the code, I think this is the nicer solution) *or* make the 'pre'
element do something like:
"<pre class="src src-emacs-lisp" style="color:#edebc4; background-color:black>"
Sure, I could hack it but has anyone already solved this problem?
Thanks in advance!!
Dirk.
Op Tue 19 May 2009, om 23:07 (+0300) schreef Dirk-Jan C. Binnema:
> Op Tue 19 May 2009, om 21:10 (+0200) schreef Dan Davison:
> >
> > I think what you are describing is achieved by
> >
> > * some heading
> > #+BEGIN_SRC perl
> > print "hello, world!";
> > #+END_SRC
> >
> > Then you just export the buffer as HTML.
> >
> > See
> >
> > http://orgmode.org/manual/Literal-examples.html#Literal-examples
--
Dirk-Jan C. Binnema Helsinki, Finland
e:djcb@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C
next prev parent reply other threads:[~2009-05-25 18:04 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
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 ` Dirk-Jan C. Binnema [this message]
2009-05-25 18:33 ` html export with htmlized code blocks [SOLVED, but...] 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
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=20090525180436.GB6128@mindcrime \
--to=djcb.bulk@gmail.com \
--cc=djcb@djcbsoftware.nl \
--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).