Initial attempt at xref forward and backward commands #1137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since switching to
eglot
, in large codebases I've noticed that Xref lacks a good way to quickly traverse back up through the stack. By the time you're ten or twenty files deep it's quite painful. Consult definesconsult-global-mark
which nearly works for navigating the xref stack (try(consult-global-mark (car (xref--get-history)))
), but doesn't properly update the state of the stack.This is an initial attempt at defining consult commands for navigating backward and forwards through the stack, and I'm opening it early to gauge interest and for discussion. It's probably not very idiomatic and shipping it might need modifications to
xref
itself, so we don't need to hit a private API for the history.