Closed ibhagwan closed 2 years ago
Yeah this was an intentional design decision. The reason behind it was to make navigations easier when you had really large hunks.
If more plugin users dislike it, I am open to changing it.
more plugin users dislike it, I am open to changing it.
Not sure how I feel about it yet, in some ways it’s beneficial when you have really large hunks but it doesn’t make much sense when you have small 2-3 line hunks, perhaps it’s best to have a setting or the ability to send hunk_down
a call option to determine behavior, either blanket jump to next hunk or perhaps minimum number of lines in a hunk to trigger end of hunk navigation?
Ty @tanvirtin!
Currently, on hunks that span multiple line,
hunk_up|down
sends you to the next edge of the hunk, would be nice to have the ability to jump to the next hunk directly.The behavior is pretty consistent and the logic works the same for
hunk_up
so I'm assuming it's a feature and not a bug.Given the file below, the first
hunk_down
sends you to line 2 and then the nexthunk_down
sends you to line 3, to get to the 2nd change (line 5) I have to press myhunk_down
keybind 3 times: