You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I build and use wren_cli with a dark them on MacOS, the gray color comes up as black, and so is invisible.
This is the color used for the command prompt, and many other items (like braces, dot, parens, etc).
I found that changing the static color value in src/module/repl.wren fixes the problem for me.
But I would like verification from others on MacOS and also LInux (KDE, Gnome).
Here's the simple code change, around line 400 in repl.wren.
In many setups dark gray (in the 16 colors) turns out to be black... that's actually the correct color if that's what the theme specifies... the problem here I think is really we should be using the "default color", not grey... so that would be a different fix.
Most terminals, apart from the basic set of 8 colors, also support the "bright" or "bold" colors. These have their own set of codes, mirroring the normal colors, but with an additional ;1 in their codes:
If a theme is setting 30;1 to black that sounds like a broken them IMHO... but again if someone rmakes a good argument what we really mean is "default" vs "grey" we could perhaps witch to the default color (39) in the place of grey in those places that made sense.
When I build and use wren_cli with a dark them on MacOS, the gray color comes up as black, and so is invisible.
This is the color used for the command prompt, and many other items (like braces, dot, parens, etc).
I found that changing the static color value in
src/module/repl.wren
fixes the problem for me.But I would like verification from others on MacOS and also LInux (KDE, Gnome).
Here's the simple code change, around line 400 in repl.wren.
If you make the change, you need to regenerate the
repl.wren.inc
file using :util/wren_to_c_string.py
Let me know. If others have this problem, I can fork the repo as send over a pull request (PR).
The text was updated successfully, but these errors were encountered: