----
-# wiki\_file\_regexp and RCS ,v files
+# Textile Plugin
-I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings.
+It was trivial, but I put together a plugin that uses the Textile markup
+language, which I find to be the most superior of the various options for
+that sort of thing. Where or how do I submit it for inclusion?
-Also I don't see wiki\_file\_regexp documented. Because it is used with $config{wiki\_file\_regexp} I assume it can be set in the ikiwiki.setup.
-I added a comma to it in my IkiWiki.pm in the defaultconfig(). But that was wrong (so I reverted back), because then the ,v files were copied to my www tree.
+> You can post it to [[plugins/contrib]]. --[[Joey]]
-What is the correct way to include ,v RCS revision files in my source tree without receiving the "bad" messages and without copying over to www tree?
+>> Thanks. I tried using the "Add new post" form there, but apparently made a [mess of things somehow](http://ikiwiki.kitenet.net/contrib/textile___40__third-party_plugin__41__.html). Sorry about that.
--- [[JeremyReed]]
+>>> No problem, the contrib form had the wrong rootpage setting. I've fixed
+>>> it up and moved it to the right place. A copyright statement would be
+>>> nice.
-> Add the ,v to the $config{wiki_file_prune_regexps} array. This is how we
-> skip equivilant files from other revision control systems too.
-> --[[Joey]]]
+> How does one go about making a markup language added by means of a plugin, the default markup language. In other words, I would like the index page to be written in Textile.
+> If I include a index.txtl (where txtl is the extension I have assigned to be handled by the textile plugin), ikiwiki will ignore it and make a new index.mdwn.
+
+>> Sounds like a bug; it should be configurable via `default_pageext`, but
+>> I suspect that currently if there are two competing files with different
+>> extensions that make the same page, they fight it out and some random
+>> one "wins"
+>>
+>> Until I fix that, you can avoid the one from the underlay directory by
+>> setting `underlaydir` to point to an empty directory. --[[Joey]]
+>>
+>> Ok, fixed (in svn), it will now prefer files in the srcdir over files
+>> in the underlaydir that build the same page, no matter what extension.
+
+>>> Thanks, Joey, much appreciated. --[Mazirian](http://mazirian.com)
----
-# Textile Plugin
+# Access Keys
-It was trivial, but I put together a plugin that uses the Textile markup
-language, which I find to be the most superior of the various options for
-that sort of thing. Where or how do I submit it for inclusion?
+Would anyone else find this a valuable addition. In oddmuse and instiki (the only other
+wiki engines I am currently using, the edit, home, and submit link tags have an
+accesskey attribute. I find it nice not to have to resort to the mouse for those
+actions. However, it may not be something everyone appreciates. Any thoughts?
+--[Mazirian](http://mazirian.com)
-> You can post it to [[plugins/contrib]]. --[[Joey]]
+----
+
+# Editing the style sheet.
+
+It would be nice to be able to edit the stylesheet by means of the cgi. Or is this possible? I wasn't able to achieve it.
+Ok, that's my last 2 cents for a while. --[Mazirian](http://mazirian.com)
+
+----
+
+# Disable build/install requirement on PerlMagick
+
+Some installs of PerlMagick require X11. I tried to first disable using "img" by using "--disable-plugin img"
+in the Makefile. But still failed. My workaround was to remove "img" from the bundle in IkiWiki/Plugin/goodstuff.pm
+before building. What is the recommended way to install ikiwiki without "img" support? --[[JeremyReed]]
\ No newline at end of file
sipb-www / ikiwiki.git / blobdiff