Jerome Gravel-Niquet

This could be an issue with Crystal itself. It does not support ignoring these when escaping HTML. For instance, they've added support to unescape all the HTML5 entities, but not...

That's interesting. I could either detect windows or maybe always use `\r\n` and there would be no harm? I need to do some testing.

What's an easy way to test this? I think we were missing this `\r\n` case in the comment section specifically. I've added it now, can you please test with master?

You're right. I'm not sure when I'll get to it though. PRs are welcome!

You should still be able to use it! If you look at this issue, it provides some hints: https://github.com/kemalcr/kemal/pull/615 You can also still include `kilt` in your dependencies and use...

There's probably more to it then that, but you'll still need to `require "kilt/slang"` yes. Kemal does something with layouts and views that's not supported out of the box with...

You should be able to use html tags directly mixed into slang. The test for it is rudimentary though: https://github.com/jeromegn/slang/blob/master/spec/slang_spec.cr#L153-L163

pug? :) `slang` templates at translated to Crystal code at compile-time.

That's a good idea.

That's currently not implemented, the equivalent from slim would be: http://www.rubydoc.info/gems/slim/frames#Trailing_and_leading_whitespace_______ Something like: ```slim a href="#" span > Contacts ```