urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

web commit by tschwinge: Answer.

master
Joey Hess 2008-01-05 09:31:06 -05:00
parent 37353bc2c3
commit a322887bb8
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/ikiwiki/wikilink/discussion.mdwn
View File

@ -20,10 +20,22 @@ BTW, ikiwiki doesn't displays the #foo anchor in the example
>> [[tag wishlist]] >> [[tag wishlist]]
>> I'd like to implement such a thing. Joey, what is this supposed to look like? >> I'd like to implement such a thing. Joey, what is this supposed to look like?
>> `\[[anchor WHATEVER]]`? --[[tschwinge]] >> `\[[anchor WHATEVER]]`? --[[tschwinge]]
>>> Why would you want to use a preprocessor directive for something that can >>> 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* >>> be more shortly and clearly done with plain HTML? Markdown is *designed*
>>> to be intermixed with HTML. --[[Joey]] >>> 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]] > The lack of the `#foo` anchor in the anchor example on [[wikilink]]
> definitely looks like a bug. --[[JoshTriplett]] > definitely looks like a bug. --[[JoshTriplett]]