-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.
+[[!template id=plugin name=sourcehighlight core=0 author="[[DavidBremner]]"]]
-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/sourcehighlight.pm)
+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.
-In the tradition of publish early and often, this just supports java
-at the moment. I will add more languages soon.
-You can add more languages by cutting and pasting the hook line; I want to add a configuration option to allow the user to specify.
+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=ikiperl.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
-One outstanding problem is that I would like to have a link to the raw source; I'm not quite sure how to manage this at them moment.
+- 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]]