Frames for pre-compiled sources report wrong path/line/column about one-small-step-for-vimkind

[jbyuki]

Thank you for the issue, I made a small change to resolve the vim runtime directory. It reads into VIMRUNTIME and appends it to the path. This allows to step into vim internal functions as well.

What I was not sure is if all the vim internal scripts resides in VIMRUNTIME . At the moment, I cannot think of a case which would not work. But you probably know more about this.

Feel free to close this issue if you feel like it is solved.

[mfussenegger]

Thanks for looking into this.

The path is now resolved correctly, but column and line are still set to 0. Is it possible to change that as well?

[jbyuki]

For precompiled lua files my initial thought is that it's impossible to get the line number. At least not using debug.getinfo. It would be nice to get it another way but my initial assumption is that this information is lost.

The new behaviour is that such precompiled modules cannot be stepped into.

From my dev setups, on windows it can be stepped into (because it's not precompiled?) and linux cannot be stepped into.

[mfussenegger]

The new behaviour is that such precompiled modules cannot be stepped into.

Thanks, that's a nice improvement over the error messages.