summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2008-01-05 09:31:06 -0500
committerJoey Hess <joey@kitenet.net>2008-01-05 09:31:06 -0500
commita322887bb8d564a98e26cd13cb22c244ec1ae917 (patch)
tree794f68dd9229bfd01efd9d3c48c523f42a75803c /doc
parent37353bc2c366fff3e6ca75cbd1d6550135d74598 (diff)
web commit by tschwinge: Answer.
Diffstat (limited to 'doc')
-rw-r--r--doc/ikiwiki/wikilink/discussion.mdwn12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/ikiwiki/wikilink/discussion.mdwn b/doc/ikiwiki/wikilink/discussion.mdwn
index dc88d7de7..c6de4597d 100644
--- a/doc/ikiwiki/wikilink/discussion.mdwn
+++ b/doc/ikiwiki/wikilink/discussion.mdwn
@@ -20,10 +20,22 @@ BTW, ikiwiki doesn't displays the #foo anchor in the example
>> [[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 <http://daringfireball.net/projects/markdown/>:
+>>>>
+>>>>> 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]]