-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Unreadable stacktrace in solarized theme #38730
Comments
It seems you have a colorscheme where some of the colors are the same as the background? Isn't the issue with the colorscheme then? |
Yes, unfortunately in solarized color8 is the same as background (and the same as And solarized is rather pretty popular scheme, so I am not going to be the only one who encounter this issue, I am afraid. |
So, there are two source of this problem (apart from bad theme itself).
|
I guess |
Two questions:
|
I guess I am the only one, who was hit by this bug and others are happy with the current situation. No need to keep it open. |
No, I'm impacted by this too. And others too: I find it unfortunate that a very popular color-theme (and other themes too, I use https://github.com/dexpota/kitty-themes/blob/master/themes/3024_Night.conf and in emacs zenburn https://github.com/bbatsov/zenburn-emacs, both sharing this issue) has to be modified to work well with stock Julia. In particular for on-boarding people to Julia. |
Solarized is a low-contrast color scheme, designed to minimize the visibility of these elements (using hue more heavily than brightness to distinguish them). It is a nice theme, but opinionated. If you don't want a low-contrast, this may not be the right theme. |
(Note, the goal of zenburn is the same: to have the lowest legible contrast. I don't know about Night.) |
iTerm2 has a handy "Minimum Contrast" slider for fixing themes, do other terminals have this? I wondered for a bit whether the logic of making VS Code has a similar setting, although its variant of "Solarized Dark" seems to be fixed already (and has |
Not all terminals have such setting. xfce-terminal do not have it (http://manpages.ubuntu.com/manpages/xenial/man1/xfce4-terminal.1.html) |
The only solution that's going to work for everyone is to name the color scheme themeable and let people design themes that work for their setups. We could ship a few and make it easy to choose between name themes. |
Solarized dark is one of the most popular colorschemes.... A lot of people just wont see the types in the stack trace and wont understand why. It probably should work by default. |
For reference: Solarized seems to be by far the most popular colorscheme in the world. We should probably test major theme changes against themes on this list to avoid issues like this in future. |
The issue described above has been fixed by #40288, so it is now straightforward to use a different color for Having support for themeable color schemes would probably not be a bad idea, but that should really be a separate issue. |
I would disagree, that PR is only half-broken workaround. Half-broken, because Pkg output has the same issues, since it uses the same philosophy of color scheme ignoring. Also it appears again when you are launching julia from shell prompt. Also, that PR has no documentation (because it was never intended to have it), so most users will be stuck, since there are no official ways to use it. I am sorry, but this is ignoring of the problem, not a solution. |
I tried it with
Documentation for this would definitely be welcome! Please keep this discussion focused on what we can do to let users customize these colors easier though. There will always be some user setups where we won't be able to guarantee a great Julia experience out of the box. We should try our best to allow users to customize the experience to make it work for their setup, but I don't think always targeting the lowest common denominator of features is a viable option. |
Related: #28690 |
I have a terminal with solarized colorscheme, and in 1.6.0 stacktrace is unreadable.
I've tried to circumvent it with overriding
:light_black
color instartup.jl
But it helped only partially. Now I can see most of the messages except the number of the line where an error has happened.
The text was updated successfully, but these errors were encountered: