SLIME uses etags' tag-marker ring in the function which is called from its version of M-. in order to use etags' facilities for popping back to where you were. This does the same.
Something I'm unsure of: the positioning of the ring-insert call. stack-mode-goto-span's docstring talks about it as if it's a pure function for extracting parts of a span, even though it actually does the jump. I think that's a docstring bug? If so I'll add a commit to fix that.
SLIME uses etags' tag-marker ring in the function which is called from its version of M-. in order to use etags' facilities for popping back to where you were. This does the same.
Something I'm unsure of: the positioning of the
ring-insert
call.stack-mode-goto-span
's docstring talks about it as if it's a pure function for extracting parts of a span, even though it actually does the jump. I think that's a docstring bug? If so I'll add a commit to fix that.