I don’t know which piece of what I’ve done got the debugger to stop at breakpoints again (it still won’t stop at
debugger; statements), but it does.
With Atom 1.0.0, I disabled all my packages except the one I wanted to debug and the Package Cop. The debugger stopped at breakpoints. So I enabled all my extensions, and it still stopped at breakpoints. Hmmm. Well, OK then.
But it disrupts the editor pane(s) when the debugger returns control to Atom.
Again using Package Cop I disabled all the packages except Package Cop and the package I’m debugging (that sure speeds up the initial Atom launch!). The debugger still stops at breakpoints. But when I continue running, control returns to Atom and the editor pane is unresponsive. No cursor, no scrolling, no response to clicks - nothing. The tree-view pane works as always.
Reloading Atom puts things right again.
What could that be from?