Starting the debug execution point on a remote file
Opened this issue · 1 comments
I am currently toying around vim-debug trying to figure out how to have the ability to execute file A.py, while debugging file B.py/C.py/etc.
With the way it is now, if you have a library that you're trying to debug, you might have to go to some main file (A.py, in this case) and debug it, and spend a potentially huge amount of time stepping through/into code to get to your B.py or C.py just so you can debug it.
Anyone have any ideas on how this can be done? I am thinking about forking and hopefully getting something working, but first i need to wrap my head around the debugger instances and junk. Any information anyone could contribute would be greatly appreciated! This is a required feature in my mind, so hopefully someone, will have an idea :)
[sorry to be so long at responding...]
That is definitely possible from a backend point of view -- the main question is how to make it work with the interface.