What do you want to change?
Follow-up to #584, where bounded expansion came up in the comments and a separate issue was suggested.
Activating an unchanged-lines gap (clicking the ▾ N unchanged lines row or pressing z) currently reveals the whole gap. Add a bounded mode: each activation reveals a limited chunk (10–20 lines) from the nearest hunk edge, repeatable until the gap is exhausted, like GitHub's PR review expansion. Full expansion stays available — for example shift+activation, or a config such as expand_step = 0.
Why?
On a gap of several hundred lines, full expansion makes the review hard to read, and the only recovery is collapsing the gap again. Most of the time the lines needed are the enclosing function head just above the hunk, or a few lines past the hunk's edge.
How? (optional)
No strong opinion on the mechanism. A per-activation step with a config override would cover both preferences discussed in #584.
What do you want to change?
Follow-up to #584, where bounded expansion came up in the comments and a separate issue was suggested.
Activating an unchanged-lines gap (clicking the
▾ N unchanged linesrow or pressingz) currently reveals the whole gap. Add a bounded mode: each activation reveals a limited chunk (10–20 lines) from the nearest hunk edge, repeatable until the gap is exhausted, like GitHub's PR review expansion. Full expansion stays available — for example shift+activation, or a config such asexpand_step = 0.Why?
On a gap of several hundred lines, full expansion makes the review hard to read, and the only recovery is collapsing the gap again. Most of the time the lines needed are the enclosing function head just above the hunk, or a few lines past the hunk's edge.
How? (optional)
No strong opinion on the mechanism. A per-activation step with a config override would cover both preferences discussed in #584.