To debug #49, I turned the debugger on, but it's being invoked by Atom, so I set it to print its output to a file instead of stdout. Then I ran it, watched it blow up, and looked at the file to see what the error was. This was really helpful in terms of figuring out the issue, how about exposing it as part of the interface in 3.0?
To debug #49, I turned the debugger on, but it's being invoked by Atom, so I set it to print its output to a file instead of stdout. Then I ran it, watched it blow up, and looked at the file to see what the error was. This was really helpful in terms of figuring out the issue, how about exposing it as part of the interface in 3.0?