-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
+[[!template id=plugin name=sourcehighlight core=0 author="[[DavidBremner]]"]]
-[my wiki](http://www.cs.unb.ca/~bremner/wiki/software/ikiwiki/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.
-you must specify a highlight_lang=>"foo,bar" in your setup file.
+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
+### 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.