-
Notifications
You must be signed in to change notification settings - Fork 3
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
Warn if 256 colors are used but not available #2173
Comments
it should be possible to bind the color scheme setting to a particular $TERM, like is done with the key remappings. otherwise users who use two different terminal types (say, xterm and vga console) on a regular basis might be mightily annoyed. |
Yup great idea! |
If user wants use 256-colors skin, he must choose the terminal with 256 colors support. I'm sure that mc should not be blamed for the fact that user tries to use 256-color skin in terminal which does not support 256 colors. mc should't do fallback itself to the any other skin. |
sorry, did you actually understand what we wrote? it doesn't seem so ... |
|
Fixed in 2169 |
Important
This issue was migrated from Trac:
egmont
(@egmontkob)This is the last bit I just did not have time and passion to add to the 256-color patch (ticket #2169).
If 256 colors are not available according to $TERM (ncurses: NCOLORS; slang: I don't know), but the requested color scheme would use any of these extended colors, currently some weird magic happens that is totally not user friendly (you end up with ugly or even unusable colors). Instead, mc could revert to the default skin (or keep the current one if dynamically changing: ticket #2165), and show an error message explaining to the user what happened.
The text was updated successfully, but these errors were encountered: