Dave Jeffery

That makes sense. Yeah, an install hook would be useful, probably best to make it a node script for compatibility, it only needs to be a few lines anyway. ```...

Thanks, did a bit of trial and error and python works ok but I found CoffeeScript works best. I quickly added dot-strings and `;;` comments so it works quite well...

Will do. Using Atom. Highlighting goes a bit horrible when using `dash-er-ized` variable names but I'll post it here if I get it working well.

Might be cool to soak up 'x is not a function' errors too: ``` javascript if (typeof(tmp$1) === 'function') { tmp$1.bind(tmp$0)(); } ```

Thinking about it... might be easier to not bind at all and just call the function in the context of the parent scope: ``` javascript tmp$0.focus(); ```

Is there a reason to make it a function call? As opposed to just `func.doc-string`?

I don't know really, I don't think there's any precedence for marking 'magic' properties in Earl Grey. I don't particularly like the aesthetics of dunder variables but they should probably...

But they are javascript properties and not Earl Grey specific.

If there was a designated format for these docstrings. Then you could probably even parse the types for argument and return values and write out some typescript. (Perhaps I've drank...

Ah ok, I didn't realise that it was enforced at compile time. Yeah, I guess I was also just confused that the semantics of `var` and `let` are completely different...