X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/7960031135e74f6d36abc4294dbadb687117222c..9fe42ec59db174f2e16b2216991c486112df8c71:/doc/ikiwiki/wikilink/discussion.mdwn diff --git a/doc/ikiwiki/wikilink/discussion.mdwn b/doc/ikiwiki/wikilink/discussion.mdwn index d81163670..c6de4597d 100644 --- a/doc/ikiwiki/wikilink/discussion.mdwn +++ b/doc/ikiwiki/wikilink/discussion.mdwn @@ -15,7 +15,28 @@ BTW, ikiwiki doesn't displays the #foo anchor in the example > No such syntax exists in markdown. ikiwiki could certainly have a > [[preprocessor_directive|preprocessordirective]] for it, though. -> +> --[[JoshTriplett]] + +>> [[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]] + > The lack of the `#foo` anchor in the anchor example on [[wikilink]] > definitely looks like a bug. --[[JoshTriplett]] @@ -27,3 +48,4 @@ Considering a hierarchy like `foo/bar/bar`, I had the need to link from the `foo/bar/bar` page to the `foo/bar` one. It would have been convenient to 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]]