"Dirk-Jan C. Binnema" writes:
> So, either I'd like the 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:
>"
7 && $t < 20)
{
fpassthrough("/var/www/daylight.css");
}
else if ( ($t > 6 && $t < 7) |
"Dirk-Jan C. Binnema" writes:
> 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 expects to find its style
> information in . And that part is not used by RSS / aggregators --
>
M-x customize-variable RET org-export-htmlize-output-type
Set the value to CSS and see what style classes are used.
I've set org-export-htmlize-css-font-prefix empty, so I can use the same
styles for org-export as I do for htmlized stuff that's floating around
on my computer from the pre-Org ye
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:
;; some comment
So, the code has all of
