-
-
Notifications
You must be signed in to change notification settings - Fork 329
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
Cursor invisible when byebug used inside minitest Progress reporter #170
Comments
@JoeCohen Can you reproduce this issue against latest master? If yes, could you provide me with a way of seeing it happening myself? |
David: ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux], with the patch Regards, On Thu, Feb 4, 2016 at 7:39 AM David Rodríguez notifications@github.com
|
Funny, I was hoping some unreleased commits would've fixed it... but since it's not happening anymore anyways I'll close. Please reopen if it reappears. Salud! |
When I set a breakpoint in a rails app using
byebug
and run tests using minitest-reporters' Progress reporter,then there is no cursor in byebug when the test hits a breakpoint.
In the Default reporter, the cursor behave properly.
(Rails 4.0.13, ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-linux], minitest 4.7.5, minitest-reporters 0.14.24).
I originally reported this as an issue for minitest-reporters. The developer suggests: "byebug should be ready for situations when cursor is hidden by the program user debug and restore it." See here. Makes sense to me as minitest does not know what the user might doing inside it.
(Sorry for merely creating an issue -- as opposed to trying to fix it -- but I have no idea how to fix the Progress reporter so this doesn't happen.)
The text was updated successfully, but these errors were encountered: