-
-
Notifications
You must be signed in to change notification settings - Fork 328
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
More user-friendly resposnses from byebug
executable
#256
Comments
👍 |
deivid-rodriguez
pushed a commit
that referenced
this issue
May 12, 2016
Merged
deivid-rodriguez
pushed a commit
that referenced
this issue
May 12, 2016
deivid-rodriguez
pushed a commit
that referenced
this issue
May 12, 2016
deivid-rodriguez
pushed a commit
that referenced
this issue
May 14, 2016
@pvalena Just released 9.0.3 with this changes, let me know what you think. |
@deivid-rodriguez It looks great! Thanks. |
Welcome! 😉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
when some
fail
is raised, it results in output of traceback with the error message in the middle, which is not easily readable for user.F. e. when no
<script.rb>
is supplied tobyebug
executable, thenfail(NoScript, 'You must specify a program to debug...')
returns
which definitely looks like program issue, not user error.
More user-friendly approach would be f.e.
The text was updated successfully, but these errors were encountered: