From: Joey Hess Date: Fri, 13 Jun 2008 15:49:22 +0000 (-0400) Subject: web commit by http://alcopop.org/me/openid/: maybe for some future backwards-compatib... X-Git-Tag: 2.50~4 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=6fe6857f7e02ff46532bf9d6838d97ffeda9025f;p=ikiwiki.git web commit by alcopop.org/me/openid/: maybe for some future backwards-compatibility killing release? --- diff --git a/doc/bugs/Spaces_in_link_text_for_ikiwiki_links.mdwn b/doc/bugs/Spaces_in_link_text_for_ikiwiki_links.mdwn index 17479aacc..023d3b379 100644 --- a/doc/bugs/Spaces_in_link_text_for_ikiwiki_links.mdwn +++ b/doc/bugs/Spaces_in_link_text_for_ikiwiki_links.mdwn @@ -35,4 +35,15 @@ reported in [[index/discussion#index11h1]]. > to a bug, so I current have no plans to bring the old behavior back. > --[[Joey]] +>> I agree that the grammar should be unambiguous. It seems to me that the +>> problem with spaces-in-wikilinks is caused by overloading the wikilink +>> and preprocessor syntax to use the same symbols. If they didn't (and is +>> there much advantage in them using the same symbols? I know in some +>> cases you have something which is a wikilink and a preprocessor directive, +>> but how often?) there'd be no problem with spaces. +>> +>> If there was ever a future, syntax-breaking major release of ikiwiki +>> (similar to python3000) I'd like to see this fixed as part of that. +>> --[[JonDowland]] + [[done]]