----
-# wiki\_file\_regexp and RCS ,v files
+# Access Keys
-I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings.
+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)
-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.
+> Maybe, although it would need to take the critisism at
+> http://www.cs.tut.fi/~jkorpela/forms/accesskey.html into account.
-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?
+>> Thank you for that link. Given that the edit link is the first thing you tab to
+>> in the current layout, I guess it isn't all that necessary. I have had a
+>> a user complaint recently that Alt-e in oddmuse was overriding his access
+>> to the browser menu.
--- [[JeremyReed]]
+----
-> 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]]]
+# 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)
-# Textile Plugin
+> I don't support editing it, but if/when ikiwiki gets file upload support,
+> it'll be possible to upload a style sheet. (If .css is in the allowed
+> extensions list.. no idea how safe that would be, a style sheet is
+> probably a great place to put XSS attacks and evil javascript that would
+> be filtered out of any regular page in ikiwiki). --[[Joey]]
-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?
+>> I hadn't thought of that at all. It's a common feature and one I've
+>> relied on safely, because the wikis I am maintaining at the moment
+>> are all private and restricted to trusted users. Given that the whole
+>> point of ikiwiki is to be able to access and edit via the shell as
+>> well as the web, I suppose the features doesn't add a lot. By the
+>> way, the w3m mode is brilliant. I haven't tried it yet, but the idea
+>> is great.
+
+----
-> You can post it to [[plugins/contrib]]. --[[Joey]]
+# Disable build/install requirement on PerlMagick
->> 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.
+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]]
-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.
\ No newline at end of file
+> I've fixed this in svn so plugins in goodstuff can be disabled. --[[Joey]]
sipb-www / ikiwiki.git / blobdiff