(no commit message)

[ikiwiki.git] / doc / plugins / contrib / sourcehighlight.mdwn

diff --git a/doc/plugins/contrib/sourcehighlight.mdwn b/doc/plugins/contrib/sourcehighlight.mdwn
index 2cf0ca5638a75007279fb778af8cb511a5af910f..2eb22e6edd01b27778e68ee41bf81dc789ded23c 100644 (file)
--- a/doc/plugins/contrib/sourcehighlight.mdwn
+++ b/doc/plugins/contrib/sourcehighlight.mdwn
@@ -1,20 +1,22 @@
+[[!template id=plugin name=sourcehighlight core=0 author="[[DavidBremner]]"]]
+
 I noticed several places in the wiki talking about similar ideas, so I decided to put a page here to point to what I am working on.
 
-I have copied otl.pm and am wrapping source-highlight (why this instead of vim highlight, I dunno, I must be a real emacs guy).  You can find more or less the latest 
-version on 
-[my wiki](http://www.cs.unb.ca/~bremner/wiki/software/ikiwiki/sourcehighlight.pm).
+I have implemented a simple wrapper around
+ [source-highlight](http://www.gnu.org/software/src-highlite/).  You can find the latest version in 
+[git](http://pivot.cs.unb.ca/git?p=ikiplugins.git;a=blob_plain;f=IkiWiki/Plugin/sourcehighlight.pm;hb=HEAD).
 You must specify `highlight_lang=>"foo,bar"` in your setup file.
 where foo and bar are the (source-supported) languages you want to
 highlight
-# Issues
+### Issues
 
-- I would like to have a link to the raw source; using will_render() and then copying the file 
-may work. 
-The discussion in [[plugins/contrib/texinfo]] seems relevant.
+- I would like to have a link to the raw source; using will_render() and then copying the file should work. 
 
 - the common case of foo.c and foo.h breaks
 because they both generate page working/dir/foo. 
 It looks to me like ikiwiki is hardcoded to strip the extension in `pagename()` (IkiWiki.pm).
 This problem with sourcehighlight needs to be fixed before it is very useful.
 
-[[DavidBremner]]
+- Is there a way to configure the colors used by source-highlight (other than editing the globally installed "default.style" file)? It would help if I could pass the command arbitrary command-line arguments; then I could configure which config file it's supposed to use. For instance, I'm not a fan of hard-coding the colors into the HTML output. IMHO, css-style formatting should be preferred. All that can be set via the command line ... --Peter
+
+> I don't really have time right now, but it should be easy to add, if you look at how src-lang is handled.  Patches are welcome :-) --[[DavidBremner]]