-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Light/Dark theme for ublue-motd acting funky #2017
Comments
I already proposed my solution for this: # Default fallback theme color
THEME="'slate'"
# Accent theme color if available
if command -v gsettings > /dev/null; then
if gsettings get org.gnome.desktop.interface accent-color > /dev/null 2>&1; then
THEME="$(gsettings get org.gnome.desktop.interface accent-color)"
fi
fi You can add some more robust checks additionally to this if you wish |
Ok now that I've played with it a bit I agree it's a bit over the top. I would color the top line, because that looks good, then color the vertical/horizontal bar cross thing, and then the icons for the bullet points. And that's it. Then leave everything else white, including the ujust section. Monochrome with the highlight box will be fine for the example commands, no need for color there. |
What you guys think about setting a lighter gray for the |
Sure, whatever looks awesome, dealer's choice! |
But I do agree that the accent colors on everything is quite over the top LOL - I LOVED it at first but as jorge said, after playing around with it a bit I believe it is a bit much indeed |
After pulling in the latest updates, now I'm getting this error upon opening any new terminals:
Is it related to this change? |
Nope! This got fixed recently, after updating you should get this fixed |
The light/dark detection method used by ublue-motd is not working too good on environments where gsettings is misreporting light/dark color schemes, like ssh sessions, distroboxes and so on. It also does not detect it properly on KDE (but given that Aurora is splitting that is not as much of a problem anymore).
I believe that by sending a patch upstream that allows configurable light/dark theme selection this might be resolved, but for now, what do you guys think should be done?
I believe we should just disable it for now or make it force dark mode
The text was updated successfully, but these errors were encountered: