please consider adding some pre-defined table style classes

[ikiwiki.git] / doc / todo / Short_wikilinks.mdwn

diff --git a/doc/todo/Short_wikilinks.mdwn b/doc/todo/Short_wikilinks.mdwn
index 7d5c65c06d7aaeb46eec9147ecd15f8e18d7c1be..b9aec91123652a7cad007f49908b5cfaa76e7f56 100644 (file)
--- a/doc/todo/Short_wikilinks.mdwn
+++ b/doc/todo/Short_wikilinks.mdwn
@@ -58,9 +58,9 @@ Other alternatives would be
 > I agree that a plugin would probably be more cumbersome, but it is very
 > doable. It might look something like this:
 
-       \[[link bar]]
+       \[[!link bar]]
 
-       \[[link bar=VeryLongPageName]]
+       \[[!link bar=VeryLongPageName]]
 
 >> This is, however, still missing specifying the link text, and adding that option would seem to me to complicate the plugin syntax a lot, unless support is added for the |-syntax for specifying a particular parameter to every plugin.
 
@@ -74,15 +74,30 @@ Other alternatives would be
 >> ... Returning to this, the syntax infact wouldn't be so bad with the |-syntax, given a short name for the plugin:
 
        [[whatever|ref 1]]
-       \[[ref 1=page_with_long_name]]
+       \[[!ref 1=page_with_long_name]]
 
 >>> A way to do this that doesn't need hacking at the preprocessor syntax
 >>> follows: --[[Joey]]
 
-       \[[link bar=1]]
-       \[[dest 1=page_with_long_name]]
+       \[[!link bar=1]]
+       \[[!dest 1=page_with_long_name]]
 
->> It also shouldn't be difficult to support non-wiki links in this same way, so that you could still link everywhere in an uniform manner, as the (still preferred by me) HTML processing approach would provide. Perhaps a plugin call wouldn't even be necessary for the links themselves: what about aliases for the normal link mechanism? Although the 'ref' call may infact be cleaner, and adding that |-syntax for plugins could offer other possibilities for other plugins.
+>>>> But this doesn't work so well for links that aren't valid keys. Such
+>>>> as stuff with spaces in it. I'd like to be able to write any kind of
+>>>> links conveniently, not just something that looks like a wikilink.
+
+>>>>> You're right, and to fix that it could be turned around: --[[Joey]]
+
+       \[[!link 1=bar]]
+       \[[!dest 1=page_with_long_name]]
+
+>> It also shouldn't be difficult to support non-wiki links in this same
+>> way, so that you could still link everywhere in an uniform manner, as
+>> the (still preferred by me) HTML processing approach would provide.
+>> Perhaps a plugin call wouldn't even be necessary for the links
+>> themselves: what about aliases for the normal link mechanism? Although
+>> the 'ref' call may infact be cleaner, and adding that |-syntax for
+>> plugins could offer other possibilities for other plugins.
 
 >>> I agree, it should be easy to make it support non-wiki links too.
 >>> We seem to have converged at something we can both live with that's