summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorhttp://www.cse.unsw.edu.au/~willu/ <http://www.cse.unsw.edu.au/~willu/@web>2009-02-07 05:47:32 -0500
committerJoey Hess <joey@kitenet.net>2009-02-07 05:47:32 -0500
commitf444d1206a75e597f65092e12dfbb061caa34ebd (patch)
tree8312d56eec27ba23afed40d64f5ac0e2f5e9708a /doc
parentfd94834c72f0682001603d01dda659ea4a4d8792 (diff)
Note todo with patch attached to solve listed problem
Diffstat (limited to 'doc')
-rw-r--r--doc/plugins/contrib/sourcehighlight.mdwn4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/plugins/contrib/sourcehighlight.mdwn b/doc/plugins/contrib/sourcehighlight.mdwn
index df480f325..07ac2086f 100644
--- a/doc/plugins/contrib/sourcehighlight.mdwn
+++ b/doc/plugins/contrib/sourcehighlight.mdwn
@@ -10,7 +10,9 @@ where foo and bar are the (source-supported) languages you want to
highlight
### Issues
-- I would like to have a link to the raw source; using will_render() and then copying the file should work.
+- I would like to have a link to the raw source; using will_render() and then copying the file should work.
+
+> You might also like to look at the [[todo/source_link]] todo. -- [[Will]]
- 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