Handle invisible transactions when navigating #210
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.
This allows next and prev navigate commands to work better with
ledger-occur
.Adds an optional argument to
ledger-navigate-start-xact-or-directive-p
which indicates whether to consider invisible points when determining if point is at beginning of xact or directive.This also refactors
ledger-navigate-prev-xact-or-directive
to use the same recursive logic asledger-navigate-next-xact-or-directive
. I'm not sure if one or the other performs better but I think the recursive logic is easier to understand and it seems reasonable they should both use the same logic.