Repository navigation
Conversation
range-diff for force push 40c04832ce → b6bb2d3903
|
range-diff for force push b6bb2d3903 → 2ec8e3f0ba
|
|
ACK 2ec8e3f
|
| default: "65000" | ||
| wrap-width: | ||
| description: "Interdiff lines longer than this are hard wrapped, repeating their diff markers; at least 4, or empty to never wrap." | ||
| default: "80" |
There was a problem hiding this comment.
| default: "80" | |
| default: "120" |
80 is very narrow
github's widest view supports a bit more than even 120, i suspect it's 130ish... not sure what it's like on 13" laptops, and mobile is not going to be great either way
There was a problem hiding this comment.
done, default is 120 now
range-diff for force push 2ec8e3f0ba → caa55ca8d0
|
range-diff for force push caa55ca8d0 → 2db6eefa69
|
range-diff for force push 2db6eefa69 → 764bc23503
|
range-diff for force push 764bc23503 → 23222d7082
|
Soft wrapped markdown puts a whole paragraph on one line, and GitHub scrolls code blocks sideways instead of wrapping them. Lines past wrap-width (120 by default) are split for reading, after the last space that fits. Each piece repeats both diff markers of its line. Repeating only the first would leave the piece's first character of text in the column of the patch's marker, where it reads as a marker. Indentation past half the width is dropped, since deeper indentation could fill a piece with spaces and show a blank line. Fixes #17
range-diff for force push 23222d7082 → 71a3e86c0e
|
closes #17. interdiff lines over
wrap-width(120 by default, at least 4) are split after the last space that fits. each piece repeats the line's diff markers and indentation, so-+stays-+and a commit message continuation keeps its indent.before:
after: