Repository navigation
V1.0.80 Code Formating for light themes does not correcly #4551
Description
Description:
In light themes, the dot (.) in code blocks is white, so you can’t see it.
The dot between object and function() basically disappears.
Tested On:
• macOS (iTerm, WezTerm)
• Windows (Windows Terminal, Wezterm)
Same issue on all of them.
I was on 0.X before and had no issues.
Activity
kommander commentedon Nov 20, 2025
Probably needs some adjustments for the syntax highlight groups in the light themes.
MonuCarpenter commentedon Nov 23, 2025
it works fine for typescript but for cpp its worst, u can not see the code properly; in dark theme its fine
fabOnReact commentedon Dec 4, 2025
I have the same problem with .vim and .less files, below an example
the text is all white which is not correct for light theme, this must be caused by your syntax highlighter (maybe bat or similar) that does not work with specific type of files
MonuCarpenter commentedon Dec 4, 2025
@fabOnReact it got fixed with the latest version, please update it
fabOnReact commentedon Dec 4, 2025
@MonuCarpenter I installed latest versione with homebrew and still have the issue. Thanks
MonuCarpenter commentedon Dec 4, 2025
@fabOnReact try ghostyy terminal
fabOnReact commentedon Dec 5, 2025
@MonuCarpenter I tried and I have the same problems
kommander commentedon Dec 5, 2025
I tried to reproduce that on macos. This looks like it happens when there is no tree-sitter parser for the given filetype. But I cannot reproduce that in any terminal. I tried with all themes in light mode and the system theme when the os is set to light mode. The font color is dark and visible for me. Can anyone give me more details on how to reproduce that? Are you using custom themes?
fabOnReact commentedon Dec 5, 2025
no, just the normal theme from opencode. I know tree-sitter because I use it in neovim, but works without problems there. Seems like tree-sitter has parser for vim files, so maybe you are not installing that parser?
kommander commentedon Dec 5, 2025
Can you try with
bunx opencode-ai@snapshot-kmdr-debug?kommander commentedon Dec 20, 2025
These have been reportedly fixed in latest versions.