Alexis Sellier

Ok, so setting `recv_timeout` to `600000` solved the issue (`infinity` doesn't seem to work, it asks for an integer timeout). It seems like it's a compromise though, because it _is_...

Hmm I see.. but are you sure it isn't an internal erlang message which is timing out in this case? Like here: https://github.com/ostinelli/misultin/blob/master/src/misultin_http.erl#L202 for example? I see how I can...

Very interesting indeed, it seems like with that fine-grained control, there can be a solution! I'll be awaiting your patch. About the chunked-encoding, the thing is I don't think it...

I had to reimplement dynamic mixins in a more robust way, to isolate them from external scope (circa 1.2.11), the problem with that is nesting won't work, so for now...

I'm pulling this in, thanks.

interesting idea! will look into it.

yea that stuff is just crazy, I'm working on a CSS interpolation rule, which looks like ``` % { ...anything in here is skipped, and outputted as-is... } ```

yea, I rewrote less from the ground-up using the treetop parsing library. This is definitely not going to work with the current code base though.

fixed in less.js, which will make its way to the main release soon. http://github.com/cloudhead/less.js

You aren't really supposed to use mixins this way, that's why.. I'll look into patching it though, because this could be interesting.