X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/4aae0841e5f1ad7ef26ef8f0ede5dca0b2ac6a24..d05d052bff599327cf43b6f00e337197f1d2ab18:/doc/index/discussion.mdwn diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index f70040abc..3c51ad99e 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -188,40 +188,28 @@ Moved to [[bugs]] -- [[Joey]] ---- -# Textile Plugin - -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? +# Access Keys -> You can post it to [[plugins/contrib]]. --[[Joey]] +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) ->> 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. +> Maybe, although it would need to take the critisism at +> http://www.cs.tut.fi/~jkorpela/forms/accesskey.html into account. ->>> 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. +---- -> 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. +# Editing the style sheet. ->> 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. +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) ->>> Thanks, Joey, much appreciated. --[Mazirian](http://mazirian.com) +---- -# Access Keys +# Disable build/install requirement on PerlMagick -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) \ No newline at end of file +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]]