whitespace test commit

[git.ikiwiki.info.git] / doc / patchqueue / index.html_allowed.mdwn

diff --git a/doc/patchqueue/index.html_allowed.mdwn b/doc/patchqueue/index.html_allowed.mdwn
index c2449a9c1a9eb67666922c3b0e713387c006ceec..5904b6096884a8b0a09015a71dc7e16cd8d51cf4 100644 (file)
--- a/doc/patchqueue/index.html_allowed.mdwn
+++ b/doc/patchqueue/index.html_allowed.mdwn
@@ -277,9 +277,27 @@ I'll attach an updated and slightly modified version below.
   >>> Presently the patch does not move `foo/index.type` as `foo/index/index.html`, but renders
   >>> it as `foo/index.html`, not because I particularly want that (except for the top-level one, of
   >>> course), but because it could be done :). This, however, conflicts with a `foo.mdwn`
   >>> Presently the patch does not move `foo/index.type` as `foo/index/index.html`, but renders
   >>> it as `foo/index.html`, not because I particularly want that (except for the top-level one, of
   >>> course), but because it could be done :). This, however, conflicts with a `foo.mdwn`

-  >>> rendered as `foo/index.html`. The easiest and cleanest way to do this, is to simply
+  >>> rendered as `foo/index.html`. The easiest and cleanest way to fix this, is to simply

   >>> not handle `index` in such a special manner -- except for the top-level one. --[[tuomov]]
 
   >>> not handle `index` in such a special manner -- except for the top-level one. --[[tuomov]]
 

+  >>>> Oh, I see, this patch doesn't address wanting to use foo/index.mdwn as 
+  >>>> an input page. Hmm. --Ethan
+
+  >>>>> No, it doesn't. I originally also was after that, but after discussing the
+  >>>>> complexities of supporting that with Joey, came up with this simpler scheme
+  >>>>> without many of those issues. It is the output that I primarily care about, anyway,
+  >>>>> and I do, in fact, find the present input file organisation quite nice. The output
+  >>>>> locations just aren't very good for conversion of an existing site to ikiwiki, and do
+  >>>>> make for rather ugly URLs with the .html extensions. (I do often type some URLs
+  >>>>> out of memory, when they're gone from the browser's completion history, and the
+  >>>>> .html makes that more laboursome.)
+
+  >>>>>> I support your decision, but now this wiki page serves two different patches :).
+  >>>>>> Can we split them somehow?
+  >>>>>> What are the complexities involved?
+  >>>>>> I think I overcomplicated it a little with my patch, and Per Bothner's gets 
+  >>>>>> much closer to the heart of it. --Ethan
+

 * This does make the resulting wikis much less browsable directly on the
   filesystem, since `dir` to `dir/index.html` conversion is only handled by web
   servers and so you end up browsing to a directory index all the time.
 * This does make the resulting wikis much less browsable directly on the
   filesystem, since `dir` to `dir/index.html` conversion is only handled by web
   servers and so you end up browsing to a directory index all the time.