Open odnoletkov opened 5 years ago
The basic logic for figuring out the diff line can be found in s:StageInfo()
. I'd recommend duplicating it as a starting point. (Don't try to DRY it up.)
If a range is given, I'd say just use the first line of it, regardless of where the cursor is.
hey @odnoletkov , it seems you implemented something like this in your fork. Are you planning to integrate it into the plugin?
See #37
Note the linked Fugitive PR is a prerequisite and the current bottleneck.
It would be great to have
:{range}Gbrowse
working for commit objects. Especially useful for doing code reviews.Sample URL:
Anchor format is:
with
L
line number is relative to the origin, withR
to the resultCouldn't find a way to select a range in this view, for selected range can either route to the first line or to the cursor position.
As far as I understand for
commit
fugitive currently doesn't provide path and line numbers, changing that should be most of the work.