After you've finished debugging something the point should go back to the invocation place

[bbatsov]

Not sure whether to call this a bug report or an improvement. Personally I find it annoying that when I'm done debugging something the point stays in the source file of the thing I was debugging instead of going back to the place I was when the debugger was triggered.

edebug behaves as I would expect, so likely a bug, but still...

[Malabarba]

Agree. This has been bothering me too.

[sooheon]

Interestingly, while investigating #1589, I found that entering debugger with special-lispy-eval would return point to where the debugger was triggered.

Ah just tested it with separate files, in that case, no the same wrong behavior is seen. But within the same file, the point moves back to the calling function correctly.

[bbatsov]

@Malabarba will you have time to address this for 0.12?

[Malabarba]

No. I'm not super sure if or how I want to fix this. Due to cider evals being asynchronous, we have some fundamental limitations that Edebug doesn't have.

I could just store the place somewhere, and then jump back to it after each step. But I think that would lead to a crappy experience in some corner cases, while making the average case marginally better.

I'd rather keep sitting on this until I have a better idea.

[bbatsov]

Won't a good first step be to store the initial location and go back there only if someone presses quit? It's just one use-case, but it's a pretty common one.

[Malabarba]

Hm. That's still more of a patch than a fix, but I like it enough. :-)

I'll try to get it done tomorrow.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!