X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/dc841f26b4a2a062514a0d50d7f81519a99ada49..ea50434091b2e87d585fc6aa0d7203baf229e5b5:/doc/index/discussion.mdwn diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index e86d08ffb..9373ec187 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -144,6 +144,8 @@ Any plugins or support for exporting to LaTeX? >> >> --JeremyReed +>>> Have a look at [pandoc](http://code.google.com/p/pandoc/). It can make PDFs via pdflatex. --[[roktas]] + ---- # Using with CVS? @@ -243,7 +245,7 @@ The [[todo]] page says admins can ban users. Where is this documented? I search set\_banned\_users() which led me to the CGI "preferences" form for the admin. Now logged in as an admin (as defined in my setup configuration), I see the field for this. But no details on how to use it. From the source it appears to be a space-delimited list of usernames. (I didn't test yet.) -Can you please provide a [[banned_users]] documentation about "banning" users function linked from the [[Features]] page and maybe [[security]] page and linked from the "preferences" for the admin? +Can you please provide a [[/banned_users]] documentation about "banning" users function linked from the [[Features]] page and maybe [[security]] page and linked from the "preferences" for the admin? (I don't do this myself as I am unsure about this and still reading the code about banning users.) ---- @@ -254,5 +256,38 @@ The [[features]] page, the [[todo]] page and the [[usage]] manual page say pages Where is locking pages documented? ... A moment later, from searching source I found this is configured via the preferences for the admin and that links to [[pagespec]]. -Can you please provide a [[page_locking]] doc about locking pages linked from the [[features]] page and elsewhere? And have that link to [[pagespec]]? +Can you please provide a [[/page_locking]] doc about locking pages linked from the [[features]] page and elsewhere? And have that link to [[pagespec]]? (I don't do this myself as I am unsure about this and still reading the code about locking pages.) + +---- + +# RecentChanges should show path to wiki sub-pages? + +The RecentChanges only shows the final file name for the recently changes file, +for example "discussion". It would be more useful to see "index/discussion" +or the path to the sub-page. I think this is handled by the htmllink() routine. + +>> IMHO it's a good idea and I like it. Often I can see changes in +>> any discussion page, but I don't know without clicking the link +>> what discussion was changed. + +>> However, I can see one problem here. You can commit via command line +>> changes in many pages. It will be displayed ugly then, because probably +>> a width of the RecentChanges page will be greater then a width of +>> user's browser. I hate these pages. So I propose to display a list of +>> changed pages in a column, not in a row. --Pawel + +---- + +# Should not create an existing page + +This might be a bug, but will discuss it here first. +Clicking on an old "?" or going to a create link but new Markdown content exists, should not go into "create" mode, but should do a regular "edit". + +---- + +# Refreshing RecentChanges page + +What do you think about refreshing RecentChanges page (via Meta Refresh Tag)? +It can be useful for users like me which rather prefer watching the last changes +in WWW browser tab than subscribing to page. --Pawel \ No newline at end of file