amCoffee

OK, but "Customize" opens a blank page...

OK, but "Customize" opens a blank page...

Throws when accessing `window`: > @ RangeError: Maximum call stack size exceeded at Object.window.__amCoffee__.process (<anonymous>:5:463) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) > this RangeError: Maximum call stack size exceeded at Object.window.__amCoffee__.process (<anonymous>:5:463) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) > window RangeError: Maximum call stack size exceeded at Object.window.__amCoffee__.process (<anonymous>:5:463) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) > window is @ true

Throws when accessing `window`: > @ RangeError: Maximum call stack size exceeded at Object.window.__amCoffee__.process (<anonymous>:5:463) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) > this RangeError: Maximum call stack size exceeded at Object.window.__amCoffee__.process (<anonymous>:5:463) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) > window RangeError: Maximum call stack size exceeded at Object.window.__amCoffee__.process (<anonymous>:5:463) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) at Object.window.__amCoffee__.process (<anonymous>:5:500) > window is @ true

good

good

Instead of "window.name" can use "@name" for quick access to the debugger context ... super usefull tool, and love the autocompletion and the tooltip for autocompletion ! keep going on and as said just add some ".toString()" for Dates and this sort of object !

Instead of "window.name" can use "@name" for quick access to the debugger context ... super usefull tool, and love the autocompletion and the tooltip for autocompletion ! keep going on and as said just add some ".toString()" for Dates and this sort of object !

Deal breaker: running "new Date()" outputs "{}" instead of "Sat Jul 18 2015 17:12:13 GMT-0700 (PDT)". How can I trust this?

Deal breaker: running "new Date()" outputs "{}" instead of "Sat Jul 18 2015 17:12:13 GMT-0700 (PDT)". How can I trust this?

It's great! I do wish that I could use a local context, because assigning something to a variable and then having that variable undefined was confusing at first. But this is still a great extension! One step closer to a JS-free world!

It's great! I do wish that I could use a local context, because assigning something to a variable and then having that variable undefined was confusing at first. But this is still a great extension! One step closer to a JS-free world!

Sadly, it doesn't work in the context of the debugger which makes it totally useless for most (if not all) of my use cases.

hay

Please make it use the context of the debugger.

Please make it use the context of the debugger.

very good！！！

very good！！！

Should be the default console.

Should be the default console.

That's what I was looking for! Excellent!

That's what I was looking for! Excellent!

It doesn't seem to use the context of the debugger so it isn't very useful.

It doesn't seem to use the context of the debugger so it isn't very useful.

Great autocompletion! Wish the standard console had the same behaviour. But what about multi-line insertion?

Great autocompletion! Wish the standard console had the same behaviour. But what about multi-line insertion?

This is superb! I do seem to have a problem assigning to variables, but I'm hoping the project continues and the minor problems are solved. BTW: I can assign to existing objects in the global space so not all that bad. My guess is I'm doing something silly. Hey, figured out the assignment problem: simply place the variable in the global space: @foo = .... window.foo = ... Makes sense. Doh! Just noticed in the Overview slide panel the use of @foo = ... I wish I could give it 6 stars.

This is superb! I do seem to have a problem assigning to variables, but I'm hoping the project continues and the minor problems are solved. BTW: I can assign to existing objects in the global space so not all that bad. My guess is I'm doing something silly. Hey, figured out the assignment problem: simply place the variable in the global space: @foo = .... window.foo = ... Makes sense. Doh! Just noticed in the Overview slide panel the use of @foo = ... I wish I could give it 6 stars.

$('body') returns jibrish functions I don't want! How can I see objects like the way default chrome console show?

$('body') returns jibrish functions I don't want! How can I see objects like the way default chrome console show?

I just spent 3 days writing this extension and finally I have discovered that it already exists

I just spent 3 days writing this extension and finally I have discovered that it already exists

rocks!

rocks!

Couldn't assign to variables?

Couldn't assign to variables?

The best coffee console AFAIK

The best coffee console AFAIK

This is the best coffeescript console tool I've ever used! The autocomplete is so handful that could even remind me the syntax I partially forgot. To developer, are you trying to make me get rid of native javascript forever? I like the logo by the way :)

This is the best coffeescript console tool I've ever used! The autocomplete is so handful that could even remind me the syntax I partially forgot. To developer, are you trying to make me get rid of native javascript forever? I like the logo by the way :)