web commit by http://ptecza.myopenid.com/: Bug report

[git.ikiwiki.info.git] / doc / index / discussion.mdwn

diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index 8cc9ec8814e1453c74f95b4d4cc6b73eb9869f46..69e612896b8e860dc80a81f08dc94f327d0dd5c6 100644 (file)
--- 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?
@@ -265,3 +267,19 @@ 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".
\ No newline at end of file