summaryrefslogtreecommitdiff
path: root/doc/plugins
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-10-26 19:43:57 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-10-26 19:43:57 -0400
commit65bf71d387ba406d4fcf697d76151b6953176cf8 (patch)
tree22e6954f3472aefb220dec883fecb12663a70278 /doc/plugins
parente8652cb0a55e6c458b700a25281eac3f2197a8d2 (diff)
organizing and pulling together syntax highlighting info
Diffstat (limited to 'doc/plugins')
-rw-r--r--doc/plugins/contrib/sourcehighlight.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/plugins/contrib/sourcehighlight.mdwn b/doc/plugins/contrib/sourcehighlight.mdwn
index 2eb22e6ed..fb368945b 100644
--- a/doc/plugins/contrib/sourcehighlight.mdwn
+++ b/doc/plugins/contrib/sourcehighlight.mdwn
@@ -20,3 +20,8 @@ This problem with sourcehighlight needs to be fixed before it is very useful.
- 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]]
+
+Note that [[Will]] wrote a plugin that uses source-highlight also. It's
+available
+[here|todo/automatic_use_of_syntax_plugin_on_source_code_files/discussion]].
+--[[Joey]]