An unknown terminal background makes the chart text unreadable on light terminals and Windows
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 75/100
Research direction
Start with the fallback in src/app.rs:262-265 and the chrome colour in src/primer.rs:278; trace how unknown terminal appearance affects cell rendering near src/app.rs:638. Then inspect the help overlay and README.md:119-121. Done means unknown backgrounds use the terminal's default chrome text colour, the overlay mentions --theme light, and the Windows README gives the required --graphics sixel --cell WxH options.
Written by the indexing model from the issue text.
Description
Today — When the terminal does not report its background (OSC 11), the appearance falls back to Dark (src/app.rs:262-265). The chrome text is then #f0f6fc (src/primer.rs:278). On a white terminal that is about 1.07:1 contrast, so the header and month labels are effectively invisible. Sixel edges are composited against #0d1117 too, so they show dark halos (src/app.rs:638). This hits every native Windows run, because term.rs:110-121 never probes there. It also hits mosh, multiplexers that don't forward OSC 11, and anyone affected by the late-reply problem. Meanwhile README says Windows Terminal draws pixels (README.md:119-121), though Windows never probes for them.
Fix
- When the appearance is unknown, draw chrome text in the terminal's default colour (
Color::Reset) and colour only the cells. Mention--theme lightin the help overlay. - Correct the README on Windows: say that it needs
--graphics sixel --cell WxH.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 1
- Avg merge
- 17h 38m
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vyncint/mossaic
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
vyncint/mossaic#57 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 75/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
area:ci kind:bug priority:p3 ready
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
srikanth235/centraid#1155 ·
Maintainers usually reply within 1 day
-
dotfiles: failed batch untrack removes earlier tracking declarationsPossibly taken @jdx claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days