How about adding debug commands such likes continue or run?

[d4l3k]

How about adding debug commands such likes continue or run?

[cosmos72]

I guess @jkryanchou was proposing to enhance gopry with the typical debugger functionality "next",
which executes one statement, then stops execution and returns to debugger prompt
(or, in this case, gopry prompt) waiting for further commands from the user.

If I understand correctly how gopry is implemented, adding this feature seems difficult: it would require injecting gopry.Pry() or something similar after every statement in the code, in order to trasfer control to gopry after every statement, and let it decide whether to resume execution or show a prompt.

[d4l3k]

This is just a wrapper around the go command so all the standard commands should just work. Have you found something that doesn't work?

If so, please provide the logs and how to reproduce.

[jkryanchou]

@d413k Hi, I add more details about my confusion on using go-pry. wish that features could be added into go-pry

[d4l3k]

I'm pretty sure you can just do

a = 1
exit

And have it continue as you've described

[jkryanchou]

@d4l3k Modify a =2 and press exit command? It doesn't work.

[d4l3k]

Yep. It'd be pretty painful

[jkryanchou]

@d4l3k OK, I got it.