New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide entry point for color customization #41791
Comments
Is that different from the current mechanism where you can modify
|
Could be discussed in #41435? |
Yes it could, but this proposal can be implemented before #41435 is fully resolved. As far as I understand #41435 is mostly about proper way of defining configuration, like TOML format and whether to use hex colors or meaningful names. But at some point somebody have to go through the code base and change all hardcoded values to config references. This proposal can be considered as low-level implementation config-agnostic detail. You can have any config setup you want and translate it to |
No, it is not the same. Changing |
What we have now is https://docs.julialang.org/en/v1/manual/environment-variables/#REPL-formatting. |
Julia uses hardcoded colors for generating output (for example stacktraces) and unfortunately color choice is not always suitable for all users for various reasons.
I propose to use the following approach instead of colors hardcoding:
This simple change does not provide full-fledged color theme switching by itself (this probably should be implemented #41435), but it provides an entry point for all future color theme related stuff. I.e. all user level convenience functions would just modify this variable one way or another. And anyway this proposal allows color customization right here and now (maybe slightly cumbersome) unlike the current situation.
Implementing this feature looks like a good beginner PR, doesn't require large modifications of the code base and it solves color issues.
The text was updated successfully, but these errors were encountered: