name "WIKI CUSTOM" above to find it easy to identify custom patches to
dokuwiki beyond having raw as-per-upstream code. then "geshi" as to
what was modded. this mods geshi and adds a config var. documentation
here:
/* new config - patches to dokuwiki enabled this. this is a directory
* realtive to 'datadir' config above where we store metadata right in the
* wiki itself to holid linking and documentation for keywords in specific
* languages like c, lua, cpp, js, python etc. you need the below directory
* and then like
* $dir/$language/keyword-link.txt
* #dir/$language/keyword-list.txt
*
* where $dir is the below base dir and $language is the lang in a code
* block like c, cpp, js etc. so for example you may have:
*
* docs/generated/c/keyword-link.txt
* docs/generated/c/keyword-list.txt
*
* inside your "pages" dir for the wiki. the link file is simply a base url
* pattern that allows you to direct where a detected keyword link is pointed
* to such as:
*
* /docs/generated/c/keywords/{FNAMEL}
*
* this replaces {FNAMEL} with the keyword. so if ou have in the wiki there
* a keywords directory and keyword.txt - this cam be the documentation for
* that keyword. this is done to alllow auto-linking of code examples as
* well as anything else code-related to appropriate documentation for a
* project without people having to hand link in everything all the time,
* much like what doxygen does, but in dokuwiki. right now it only works
* inside code blocks syntax hilighted by geshi
*/
$conf['code_extn'] = 'docs/generated';
you might ewant to set:
/* max cache time for a wiki pagee - this is so that code keyword
* hilighting works even if a page doesn't have a
* ~~NOCACHE~~ directive in it. if it has this in it, then code keyword
* extension hilighting is updated immediately
*/
$conf['cachetime'] = 3600;
(max page cache = 1h).
Andy Williams
Carsten Haitzler