Repository navigation
Support line ranges in :Gbrowse for commits #36
Description
Activity
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.
- added a commit that references this issue
on Feb 10, 2019 - added 2 commits that reference this issue
on Aug 21, 2019 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.
- added a commit that references this issue
on Sep 18, 2019 - added 2 commits that reference this issue
on Apr 6, 2021
It would be great to have
:{range}Gbrowseworking for commit objects. Especially useful for doing code reviews.Sample URL:
Anchor format is:
with
Lline number is relative to the origin, withRto 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
commitfugitive currently doesn't provide path and line numbers, changing that should be most of the work.