umputun / revdiff / 24939288252

90%

master: 90%

Pull #151

github

docs: clarify ANSI envelope preservation reasoning in scrollbar

Copilot review on PR #151 flagged the byte-width claim as misleading.
The current text said "both track and thumb share the same UTF-8 byte
width" / "Both glyphs are 3-byte UTF-8 so the slice replacement
preserves the surrounding ANSI envelope" — but scrollbarThumbRune is
the bold-wrapped string "\x1b[1m┃\x1b[22m" (12 bytes), not 3, so the
implied byte-equality argument was wrong.

Reword both spots (godoc on applyScrollbar, CLAUDE.md gotcha entry) to
state the actual mechanism: the slice operation finds the rune via
LastIndex and replaces only that rune, leaving prefix/suffix bytes
(border fg/bg ANSI) intact regardless of the thumb's added SGR wrap.
The 1-cell display width of ┃ and │ is what keeps geometry stable —
that's separate from envelope preservation.

Related to #151.

120 of 121 new or added lines in 2 files covered. (99.17%)

8527 of 9524 relevant lines covered (89.53%)

549.16 hits per line