(no commit message)

[git.ikiwiki.info.git] / doc / todo / syntax_highlighting / discussion.mdwn

diff --git a/doc/todo/syntax_highlighting/discussion.mdwn b/doc/todo/syntax_highlighting/discussion.mdwn
index adae9c1fb044b3b89ccfa308b81bc14b29634f64..27cb7084b77497ff2996955b48713964a42d8b00 100644 (file)
--- a/doc/todo/syntax_highlighting/discussion.mdwn
+++ b/doc/todo/syntax_highlighting/discussion.mdwn
@@ -2,6 +2,10 @@ sourcehighlight is annoyingly slow, but it does support wiki directives
 in comments. See [here](http://www.cs.unb.ca/~bremner/teaching/java_examples/snippet/ListMerge/)
 for an example (tags).
 
 in comments. See [here](http://www.cs.unb.ca/~bremner/teaching/java_examples/snippet/ListMerge/)
 for an example (tags).
 

+> I think that is just a result of it expanding directives, and wikilinks,
+> everywhere in the file, which is generally a possible problem..
+> --[[Joey]]
+

 * * * * *
 
 I think having the option to choose source code page types from the
 * * * * *
 
 I think having the option to choose source code page types from the


@@ -10,3 +14,15 @@ to contribute programs (say `.pl` files) or code snippets (like, for
 example, the Elisp area of the EmacsWiki).  Actually, would there any
 other way to create a `.pl` file without write access to the
 repository?  --[[JasonBlevins]]
 example, the Elisp area of the EmacsWiki).  Actually, would there any
 other way to create a `.pl` file without write access to the
 repository?  --[[JasonBlevins]]

+
+> Well, you can upload them as an attachment if the wiki is configured to
+> allow it. Having them in the drop down becomes a problem when there are
+> so many wacky extensions in there that you can't find anything.
+> --[[Joey]]
+
+>> I should just note that the
+>> [[sourcecode|todo/automatic_use_of_syntax_plugin_on_source_code_files/discussion]]
+>> plugin only adds the file extensions listed in the config.  This shouldn't cause
+>> massive drop-down menu pollution.  -- [[Will]]
+
+>>> That seems to be the way to go! --[[Joey]]