You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I come from a Ruby background and am used to pry and byebug as my main debuggers, and spent a good 20mins wondering why I couldn't inspect variables with this debugger when stepping/moving worked fine.
I realize that l prints all the locals out, but I'm wondering how I can inspect individual variables...
And then out of frustration I type in:
debugger.lua> asdfasdf
debugger.lua>
And notice that the prompt doesn't react and then I'm like ohhh when it doesn't understand a command it just pretends like nothing happened.
Cue these attempts:
debugger.lua> pp(transitions)
debugger.lua> p
Error: command 'p' not recognized.
Type 'h' and press return for a command list.
debugger.lua> pp
debugger.lua> h
[.. help output ..]
debugger.lua> p transitions
transitions => {"Not Ready" = {}}
I was expecting the output of p and pp to tell me what arguments they were expecting.
Even more confusing is that when you do type in the right single character command but with the wrong arguments, it says Error: command 'p' not recognized - which is arguably even more misleading 🤣
Anyway. Just throwing my 2 cents in here. I'm still too much of a lua noob to attempt to fix this myself, but if you think it's a worthy addition, I can make an attempt.
Edit: Turned out to be an easy fix - I created a PR.
The text was updated successfully, but these errors were encountered:
vyder
added a commit
to vyder/debugger.lua
that referenced
this issue
May 5, 2020
I come from a Ruby background and am used to
pry
andbyebug
as my main debuggers, and spent a good 20mins wondering why I couldn't inspect variables with this debugger when stepping/moving worked fine.I was doing variations of this:
I realize that
l
prints all the locals out, but I'm wondering how I can inspect individual variables...And then out of frustration I type in:
And notice that the prompt doesn't react and then I'm like ohhh when it doesn't understand a command it just pretends like nothing happened.
Cue these attempts:
I was expecting the output of
p
andpp
to tell me what arguments they were expecting.Even more confusing is that when you do type in the right single character command but with the wrong arguments, it says
Error: command 'p' not recognized
- which is arguably even more misleading 🤣Anyway. Just throwing my 2 cents in here.
I'm still too much of a lua noob to attempt to fix this myself, but if you think it's a worthy addition, I can make an attempt.Edit: Turned out to be an easy fix - I created a PR.
The text was updated successfully, but these errors were encountered: