-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pause on debug #12
Comments
With the latest update, which unbuffers the output, I can at least see the debug prompt (using binding.pry). The next step is to accept user input for the debugger. |
+1 for this, I love this package, adding debugging support would make it more amazing :) |
The |
There's another way. I use https://github.com/Mon-Ouie/pry-remote. That alone would work if you want to jump to a terminal to finish the pry session. I elect to use the https://github.com/webBoxio/atom-term2 package for atom, then I can pry debug without leaving atom :) |
In
ruby test
for Sublime Text, test runs jump overdebug
orbyebug
statements and finish execution. In Atom, the code stops (I have verified this behavior forbyebug
only).I cannot find a way to resume. Of course the best would be if there were a way to actually step through code from Atom, but failing that,
ruby test
runs should not freeze on these statements.UPDATE: Indeed when
ruby-test
stops on abyebug
statement, there's no apparent way to kill it without closing Atom.The text was updated successfully, but these errors were encountered: