diff options
author | Joey Hess <joey@kodama.kitenet.net> | 2007-11-07 11:45:39 -0500 |
---|---|---|
committer | Joey Hess <joey@kodama.kitenet.net> | 2007-11-07 11:45:39 -0500 |
commit | 3f85a480098641fd07e4dec8693d025634ba8017 (patch) | |
tree | 58362b4eae9c9ee8022707056e6fd6e48dc1c3f2 | |
parent | feca3a995bdd4eef3684999d1aa8bf2d36b85801 (diff) |
thoughts
-rw-r--r-- | doc/plugins/contrib/texinfo.mdwn | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/plugins/contrib/texinfo.mdwn b/doc/plugins/contrib/texinfo.mdwn index 07e506948..cb2bf038c 100644 --- a/doc/plugins/contrib/texinfo.mdwn +++ b/doc/plugins/contrib/texinfo.mdwn @@ -29,6 +29,23 @@ is a N-to-M mapping: How to teach this to ikiwiki? +> As far as multiple input files, you'd need to use add_depends() +> to let ikiwiki know that a change to any of those files should cause a +> rebuild of the "main" file. I guess you'd also have to somehow deal with +> it wanting to render pages for each of the helper files. Not quite sure +> what the best way would be to avoid that. +> +> Ikiwiki is perfectly happy with a page creating other files (see eg, the +> img and teximg plugins, as well as the inline plugin's rss generation). +> The will_render() function supports that. +> +> What hasn't been done though is a page creating more than one other _page_. +> Perhaps you could call IkiWiki::genpage by hand for each additional page. +> You might also want to manipulate each data structure that tracks info about +> pages, adding the additional pages to them, so that they're first class +> pages that work as pages everywhere in ikiwiki (ie, can be inlined, +> appear in a site map, be linked to, etc). Not sure how to do that, +> and perhaps you could get away without doing it actually. --[[Joey]] ## Copyright and Licensing Snippets |