-After using it for a while, my feeling is that hyperestradier, as used in
+After using it for a while, my feeling is that [[hyperestraier]], as used in
the [[plugins/search]] plugin, is not robust enough for ikiwiki. It doesn't
-upgrade well, and it has a habit of sig-11 on certian input from time to
+upgrade well, and it has a habit of sig-11 on certain input from time to
time.
So some other engine should be found and used instead.
>>> it. Thank you java.. The C++ version seems like a better choice to me
>>> (packages are trivial). --[[Joey]]
+> Might I suggest renaming the "search" plugin to "hyperestraier", and then creating new search plugins for different engines? No reason to pick a single replacement. --[[JoshTriplett]]
+
<pre>
Index: IkiWiki/Plugin/search.pm
===================================================================
+
sub import { #{{{
- hook(type => "getopt", id => "hyperestraier",
-- call => \&getopt);
+- call => \&getopt);
- hook(type => "checkconfig", id => "hyperestraier",
+ hook(type => "checkconfig", id => "plucene",
- call => \&checkconfig);
+ call => \&checkconfig);
- hook(type => "pagetemplate", id => "hyperestraier",
-- call => \&pagetemplate);
+- call => \&pagetemplate);
- hook(type => "delete", id => "hyperestraier",
+ hook(type => "delete", id => "plucene",
- call => \&delete);
+ call => \&delete);
- hook(type => "change", id => "hyperestraier",
+ hook(type => "change", id => "plucene",
- call => \&change);
+ call => \&change);
- hook(type => "cgi", id => "hyperestraier",
-- call => \&cgi);
+- call => \&cgi);
} # }}}
-sub getopt () { #{{{