Ash Berlin-Taylor

I have raised an issue with grunt-node-tap - lets see if the author of it has any insights.

Sounds like a nice idea (your example got cut off but I think I know what you were going to say - probably you need to escape it so github...

A few things: 1. check it works for you and doesn't have any edge cases or odd behavior 2. Work out what we want to do in cases like [this](http://johnmacfarlane.net/babelmark2/?text=%3Cdiv%3EThis+*is+still*+markdown%3C%2Fdiv%3E):...

(I'm not expecting the original author to pick this up as I've let it languish for years. Just for the record) This patch goes someway to addressing HTML support but...

Support for this as a dialect should possible. Its probably not that much work if you base it on the existing standard dialect (look for Maruku how do that). Unfortunately...

As you might have noticed I did a lot of tidying up (mainly getting the test suite running again) and closing of the easier bugs on the markdown project this...

I made a start on the [gfm](https://github.com/evilstreak/markdown-js/tree/gfm) branch - Can't remember how far I've gotten though...

Yay for ambiguous markdown syntax. Cos there's not enough of that already... > And not to hijack, but I don't think GFM is feature complete without being able to update...

https://github.com/evilstreak/markdown-js#notice-unmaintained -- PR welcome though.

At times I wish I hadn't built this around regexps :( That :ship: has long since sailed. Change looks okay - could you look at what happened to the node...