X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/250e3789fee4fb2539e954f52ab356ff6d3a3978..d5e65e582a34ae2494fee493ddcb2b959e4a4bce:/doc/ikiwiki/wikilink/discussion.mdwn diff --git a/doc/ikiwiki/wikilink/discussion.mdwn b/doc/ikiwiki/wikilink/discussion.mdwn index 66b5eae06..e69fcb31b 100644 --- a/doc/ikiwiki/wikilink/discussion.mdwn +++ b/doc/ikiwiki/wikilink/discussion.mdwn @@ -17,10 +17,26 @@ BTW, ikiwiki doesn't displays the #foo anchor in the example > [[preprocessor_directive|preprocessordirective]] for it, though. > --[[JoshTriplett]] ->> [[tag wishlist]] +>> [[!tag wishlist]] >> I'd like to implement such a thing. Joey, what is this supposed to look like? >> `\[[anchor WHATEVER]]`? --[[tschwinge]] +>>> Why would you want to use a preprocessor directive for something that can +>>> be more shortly and clearly done with plain HTML? Markdown is *designed* +>>> to be intermixed with HTML. --[[Joey]] + +>>>> I tend to disagree. +>>>> It just doesn't feel right for me to put HTML code straight into Markdown files. +>>>> +>>>> Quoting : +>>>> +>>>>> The idea is that a Markdown-formatted document should be publishable as-is, as plain text, *without looking like it’s been marked up with tags or formatting instructions*. +>>>> +>>>> Also, in theorie at least, Markdown might also support other output formats than HTML. +>>>> Those wouldn't know about how to deal with the intermingled HTML code. +>>>> +>>>> --[[tschwinge]] +>>>>>Not sure \[[anchor WHATEVER]] looks any better than <a name="WHATEVER">...? --[[sabr]] > The lack of the `#foo` anchor in the anchor example on [[wikilink]] > definitely looks like a bug. --[[JoshTriplett]] @@ -34,3 +50,11 @@ Considering a hierarchy like `foo/bar/bar`, I had the need to link from the simply write [[wikilink]]s like `\[[../bar]]` (or even just `\[[..]]`?), but this doesn't work, so I had to resort to using `\[[foo/bar]]` instead. --[[tschwinge]] + +---- + +How do I make images clickable? The obvious guess, \[[foo.png|/index]], doesn't work. --[[sabr]] + +> You can do it using the img plugin. The syntax you suggested would be ambiguous, +> as there's no way to tell if the text is meant to be an image or displayed as-is. +> --[[Joey]]