Stefan van der Walt <[EMAIL PROTECTED]> writes: > Unfortunately, > > <include file="..." markup="example"/> > > no longer works (error message attached).
I found the problem and fixed it.
> A further two questions regarding the colour output:
>
> 1. How can a person surround your source code in an <example> block
> (i.e. bordered with grey background).
Use something like the following in your CSS stylesheet.
pre.example {
background-color: #708090; /* slate gray */
}
> 2. How can I control the colours used in markup? Currently, they
> seem to depend on the settings of your emacs session (i.e. I run a
> theme with dark background and light text, which means the source
> code is highlighted to have very light text. This doesn't work well
> on the white backdrop of my webpage.)
One way would be to make a function called (for example)
`my-python-mode' that switches to the desired color theme, runs
`python-mode', and switches back (don't know if switching back there
would do the right thing though ... might have to omit that and change
the theme back later). Then just use lang="my-python" in your <src>
tags.
Or make a function that changes the theme and add it to
muse-before-publish-hook, and make a complementary one to change it
back and add it to muse-after-publish-hook.
Or set the background of the published src tag to something darker in
your CSS stylesheet, as follows.
pre.src {
background-color: black;
}
--
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: Lisp, text markup, protocols -- Jabber: mwolson_at_hcoop.net
/` |\ | | | Projects: Emacs, Muse, ERC, EMMS, Planner, ErBot, DVC
|_] | \| |_| Reclaim your digital rights by eliminating DRM.
See http://www.defectivebydesign.org/what_is_drm for details.
pgp9yfrS45TKs.pgp
Description: PGP signature
_______________________________________________ Muse-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/muse-el-discuss
