bat

Summary tracks the terminal's active ANSI style in an struct so bat can re-apply it before each syntax-highlighted token (nu_ansi_term appends a full reset after every token). The struct already has a field, documented , that is initialized, cleared in , and re-emitted in — but had no match arm for SGR or , so was only ever cleared, never set. Consequence: with ANSI passthrough (the default — and both default to ), bold/dim/italic/underline survive across highlighted tokens because they are tracked and re-emitted, but strikethrough visibly disappears after the first token. This adds the missing (set) and (clear) arms, mirroring the sibling underline (/) and italic (/) arms, so strikethrough persists like every other supported attribute. Two-line behavioral change; no API change. intentionally does not reset SGR attributes yet (existing commented-out TODO), so is handled there exactly like bold/italic — no change needed. Test Plan (unit + integration). Extended the unit test to include SGR , and added covering set () and clear (). Added integration test , modeled on the existing , asserting strikethrough is re-emitted across a wrap boundary. It fails before the fix and passes after. Developed with assistance from Claude Code; reviewed & validated by me. 🤖 Generated with [Claude Code

Closes #1948. The README's "Adding new themes" section already states custom themes must be and that isn't supported — but the man page () mentioned without that clarification. This syncs the man page template with the README (the maintainer asked to "sync README and man page" in the thread). Verified against the loader: custom themes are read from via syntect's , which only picks up files (), refreshed with — so is the only supported format. Changed (the template; the generated isn't committed) + a CHANGELOG entry. _Disclosure: I use AI assistance for code review and drafting; I review and verify every change myself._