urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Thoughts

master
http://www.cse.unsw.edu.au/~willu/ 2008-11-02 05:23:25 -05:00 committed by Joey Hess
parent c2684b94b2
commit 8a901ad49c
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/todo/syntax_highlighting.mdwn
View File

@ -32,6 +32,10 @@ pages, as well as doing syntax highlighting as a preprocessor directive
we could use an external plugin..) we could use an external plugin..)
* Currently no single plugin supports both modes of operation (directive * Currently no single plugin supports both modes of operation (directive
and whole source file to page). and whole source file to page).
> This is now fixed by the [[ikiwiki/directive/format]] directive for all
> whole-source-file plugins, right?
* Nothing seems to support * Nothing seems to support
[[wiki-formatted_comments|wiki-formatted_comments_with_syntax_plugin]] [[wiki-formatted_comments|wiki-formatted_comments_with_syntax_plugin]]
inside source files. Doing this probably means post-processing the inside source files. Doing this probably means post-processing the
@ -45,6 +49,17 @@ pages, as well as doing syntax highlighting as a preprocessor directive
One approach that's also been requested for eg, One approach that's also been requested for eg,
[[plugins/contrib/mediawiki]] is to allow controlling which linkification [[plugins/contrib/mediawiki]] is to allow controlling which linkification
types a page type can have on it. types a page type can have on it.
> The previous two points seem to be related. One thought: instead of
> getting the source from the `content` parameter, the plugin could
> re-load the page source. That would stop directives/links from
> being processed in the source. As noted above, comments
> could then be parsed for directives/links later.
>
> Would it be worth adding a `nodirectives` option when registering
> an htmlize hook that switches off directive and link processing before
> generating the html for a page?
* The whole-file plugins all get confused if there is a `foo.c` and a `foo.h`. * The whole-file plugins all get confused if there is a `foo.c` and a `foo.h`.
This is trivially fixable now by passing the keepextension option when This is trivially fixable now by passing the keepextension option when
registering the htmlize hooks, though. registering the htmlize hooks, though.
@ -61,6 +76,11 @@ pages, as well as doing syntax highlighting as a preprocessor directive
extensions. The workaround is to use a directive on a wiki page, pulling extensions. The workaround is to use a directive on a wiki page, pulling
in the Makefile. in the Makefile.
> I wonder how hard it would be to make a patch where by a file with
> no `.` in the name, and a name that matches a filetype, and where
> that filetype was registered `keepextension`, then the file is just
> chosen as the appropriate type...
## format directive ## format directive
Rather than making syntax highlight plugins have to provide a preprocessor Rather than making syntax highlight plugins have to provide a preprocessor