From ba1c3553531893c107d09f4693cacdc0cb29c88c Mon Sep 17 00:00:00 2001 From: "http://smcv.pseudorandom.co.uk/" Date: Fri, 31 Jul 2009 17:14:50 -0400 Subject: I now realise that one of trail's modes is a bit flawed... --- doc/plugins/contrib/trail.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'doc/plugins') diff --git a/doc/plugins/contrib/trail.mdwn b/doc/plugins/contrib/trail.mdwn index 52dea52d6..eb233e095 100644 --- a/doc/plugins/contrib/trail.mdwn +++ b/doc/plugins/contrib/trail.mdwn @@ -13,6 +13,17 @@ This plugin can benefit from [[another_of_my_branches|todo/inline_plugin:_specifying_ordered_page_names]] but does not require it. +Bugs: + +* \[[!inline pages="..." trail=yes]] currently tries to work out + what pages are in the trail, and their order, at scan time. That + won't work, because matching a pagespec at scan time is + unreliable - pages we want might not have been scanned yet! I + haven't worked out a solution for this. I think + \[[!inline pagenames="..." trail=yes]] + ([[patch_required|todo/inline_plugin:_specifying_ordered_page_names]]) + would be safe, though. + ---- [[!template id=plugin name=trail author="[[Simon_McVittie|smcv]]"]] -- cgit v1.2.3 From 612505d76bb338b243b9cac1f8b1a4291dd7c3e1 Mon Sep 17 00:00:00 2001 From: "http://smcv.pseudorandom.co.uk/" Date: Fri, 31 Jul 2009 17:18:20 -0400 Subject: Self-review... --- doc/plugins/contrib/album.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'doc/plugins') diff --git a/doc/plugins/contrib/album.mdwn b/doc/plugins/contrib/album.mdwn index f550ca64c..395c99bce 100644 --- a/doc/plugins/contrib/album.mdwn +++ b/doc/plugins/contrib/album.mdwn @@ -65,6 +65,13 @@ The next/previous links are themselves implemented by photo, using a special template (by default `albumnext.tmpl` or `albumprev.tmpl`), in `archive`/`quick` mode. +> With hindsight, using an inline here is wrong - I should just +> run hooks and fill in the template within the album plugin. +> inline has some specialized functionality that's overkill +> here, and its delayed HTML substitution breaks the ability +> to have previous/up/next links both above and below the +> photo, for instance. --[[smcv]] + ## Writing the album The album contains one `\[[!album]]` directive. It may also -- cgit v1.2.3 From faa29aaaf33af916ebb3936d9d2bcad32b8aedd6 Mon Sep 17 00:00:00 2001 From: "http://schmonz.livejournal.com/" Date: Fri, 31 Jul 2009 18:17:53 -0400 Subject: add working CVS plugin --- doc/plugins/contrib/cvs.mdwn | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 doc/plugins/contrib/cvs.mdwn (limited to 'doc/plugins') diff --git a/doc/plugins/contrib/cvs.mdwn b/doc/plugins/contrib/cvs.mdwn new file mode 100644 index 000000000..2b51bee2b --- /dev/null +++ b/doc/plugins/contrib/cvs.mdwn @@ -0,0 +1,31 @@ +[[!template id=plugin name=cvs core=0 author="[[schmonz]]"]] + +This plugin allows ikiwiki to use [[!wikipedia desc="CVS" Concurrent Versions System]] as an [[rcs]]. + +* Diffs are against [[3.14159|news/version_3.14159]]. `cvs.pm` started life as a copy of `svn.pm`. +* `IkiWiki.pm` avoids copying CVS metadata into `$DESTDIR`. +* [[ikiwiki-makerepo]]: + * creates a repository, + * imports `$SRCDIR` into top-level module `ikiwiki` (vendor tag IKIWIKI, release tag PRE_CVS), + * creates a small post-commit wrapper to prevent `cvs add ` from being seen by ikiwiki's [[post-commit]] hook, + * configures the wrapper itself as a post-commit hook in `CVSROOT/loginfo`. +* [`cvsps`](http://www.cobite.com/cvsps/) is required (`rcs_recentchanges()` and `rcs_diff()` need it to work). +* CVS multi-directory commits happen separately; the post-commit hook sees only the first directory's changes in time for [[recentchanges|plugins/recentchanges]]. The next run of `ikiwiki --setup` will correctly re-render such a recentchanges entry. It might be possible to solve this problem with scripts like `commit_prep` and `log_accum` from CVS contrib. +* Due to the name of CVS's metadata directories, it's impossible to create `.../CVS/foo.mdwn`. On case-insensitive filesystems it's also impossible to create `.../cvs/foo.mdwn`. +* No testing or special-casing has been done with [[attachments|plugins/attachment]], but they'll probably need `cvs add -kb`. + +Having a `$HOME/.cvsrc` isn't necessary. Sure does make using CVS more livable, though. Here's a good general-purpose one: + + cvs -q + checkout -P + update -dP + diff -u + rdiff -u + +Not knowing how the tests get set up, I blindly attempted to add subversion-like tests to `t/file_pruned.t`. They fail. But the plugin definitely works. :-) + +### Code +* [`cvs.pm`](http://www.netbsd.org/~schmonz/ikiwiki-cvs/cvs.pm) +* [`cvs-IkiWiki.pm.diff`](http://www.netbsd.org/~schmonz/ikiwiki-cvs/cvs-IkiWiki.pm.diff) +* [`cvs-ikiwiki-makerepo.diff`](http://www.netbsd.org/~schmonz/ikiwiki-cvs/cvs-ikiwiki-makerepo.diff) +* [`cvs-t-file_pruned.t.diff`](http://www.netbsd.org/~schmonz/ikiwiki-cvs/cvs-t-file_pruned.t.diff) -- cgit v1.2.3 From 216a349bb92af7d408ec076b6f6f740ac735cdcf Mon Sep 17 00:00:00 2001 From: "http://schmonz.livejournal.com/" Date: Fri, 31 Jul 2009 18:37:58 -0400 Subject: specify where in IkiWiki.pm CVS metadata is avoided (wiki_file_prune_regexps) --- doc/plugins/contrib/cvs.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/plugins') diff --git a/doc/plugins/contrib/cvs.mdwn b/doc/plugins/contrib/cvs.mdwn index 2b51bee2b..1ff71d274 100644 --- a/doc/plugins/contrib/cvs.mdwn +++ b/doc/plugins/contrib/cvs.mdwn @@ -3,7 +3,7 @@ This plugin allows ikiwiki to use [[!wikipedia desc="CVS" Concurrent Versions System]] as an [[rcs]]. * Diffs are against [[3.14159|news/version_3.14159]]. `cvs.pm` started life as a copy of `svn.pm`. -* `IkiWiki.pm` avoids copying CVS metadata into `$DESTDIR`. +* `IkiWiki.pm:wiki_file_prune_regexps` avoids copying CVS metadata into `$DESTDIR`. * [[ikiwiki-makerepo]]: * creates a repository, * imports `$SRCDIR` into top-level module `ikiwiki` (vendor tag IKIWIKI, release tag PRE_CVS), -- cgit v1.2.3