[12:13:40 CDT(-0500)] <colinclark> hey yzen
[12:13:48 CDT(-0500)] <yzen> colinclark: hi
[12:13:57 CDT(-0500)] <colinclark> you were mentioning liking debugging Node.js apps with eclipse
[12:14:11 CDT(-0500)] <yzen> colinclark: yes and it's pretty nice
[12:14:19 CDT(-0500)] <colinclark> Does it show any more than the 10 stack frames that node-inspector does?
[12:14:24 CDT(-0500)] <yzen> no
[12:14:34 CDT(-0500)] <yzen> it's not really node-inspector's setting
[12:14:38 CDT(-0500)] <colinclark> yeah
[12:14:40 CDT(-0500)] <colinclark> I know
[12:15:56 CDT(-0500)] <yzen> here's the page i used to set everything uphttps://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger
[12:16:16 CDT(-0500)] <yzen> you can also debug external node apps as well
[12:16:19 CDT(-0500)] <jhernandez> ** cough ** .. eclipse? really?
[12:16:33 CDT(-0500)] <yzen> jhernandez: isn't it awesome
[12:16:34 CDT(-0500)] <yzen>
[12:16:39 CDT(-0500)] <jhernandez> xDDD
[12:16:52 CDT(-0500)] <jhernandez> not for me but for others sure!
[12:16:57 CDT(-0500)] <jhernandez>
[12:17:04 CDT(-0500)] <yzen> no kasparnet can not complaint that chrome crashes every time he's debugging
[12:17:09 CDT(-0500)] <yzen> he has no excuse any more
[12:17:13 CDT(-0500)] <jhernandez> haha
[12:17:57 CDT(-0500)] <yzen> Bosmon: you sitll use eclipse ?
[12:18:09 CDT(-0500)] <Bosmon> yzen - every day
[12:18:18 CDT(-0500)] <Bosmon> colinclark has been telling me about "what is now cool" in the node.js world : P
[12:18:22 CDT(-0500)] <yzen> Bosmon: nice so you ll find it handy
[12:18:36 CDT(-0500)] <colinclark> jhernandez: dude I'm with you
[12:18:42 CDT(-0500)] <Bosmon> I did try to get that debugger working a few years ago and it was a miserable and unrewarding experience
[12:18:45 CDT(-0500)] <Bosmon> But it sounds like it is now working?
[12:18:51 CDT(-0500)] <colinclark> all I want is a text editor
[12:19:08 CDT(-0500)] <yzen> Bosmon: yes it works well
[12:19:19 CDT(-0500)] <jhernandez> oh my god! Bosmon uses eclipse? (I just dropped a myth!)
[12:19:20 CDT(-0500)] <Bosmon> colinclark - still the ability to "scope a search within a project" is the one remanent feature from Eclipse I find useful for non-Java programming
[12:19:31 CDT(-0500)] <jhernandez> colinclark: +1
[12:19:35 CDT(-0500)] <Bosmon> It's not clear how I would do that with a simple text editor : P
[12:19:47 CDT(-0500)] <colinclark> I am a pretty inept programmer
[12:19:54 CDT(-0500)] <colinclark> so I prefer my tools to reflect that
[12:19:54 CDT(-0500)] <Bosmon> But my main question is, does the node Eclipse debugger still suffer from the 10 stack-frame limit that we have in node-inspector?
[12:19:57 CDT(-0500)] <yzen> Bosmon: you can with sublime
[12:20:08 CDT(-0500)] <yzen> Bosmon: of course
[12:20:23 CDT(-0500)] <yzen> who needs more than 10?
[12:20:35 CDT(-0500)] <jhernandez> yzen: that's true!
[12:20:36 CDT(-0500)] <jhernandez> xDDD
[12:20:58 CDT(-0500)] <Bosmon> yzen - anyone who debugs into the framework, I guess
[12:21:06 CDT(-0500)] <Bosmon> I imagine you don't find yourself doing that very much
[12:21:14 CDT(-0500)] <colinclark> It's like the Node.js version of jessm's adage, "there are always three things"
[12:21:18 CDT(-0500)] <yzen> i guess where the problem is
[12:21:24 CDT(-0500)] <colinclark> except it's "there are always 10 stack frames"
[12:22:16 CDT(-0500)] <colinclark> yzen: To that I say, "show me your pull request"
[12:23:53 CDT(-0500)] <colinclark> jhernandez: PUPPY REPORT?
[12:24:06 CDT(-0500)] <jhernandez> heh
[12:24:17 CDT(-0500)] <jhernandez> they're fine
[12:24:27 CDT(-0500)] <jhernandez> and I already have owners for all of them
[12:24:45 CDT(-0500)] <jhernandez> :]