-
Notifications
You must be signed in to change notification settings - Fork 137
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
feat: themes support +2 new themes, blue and gold #550
Conversation
@vladdoster @pschmitt @alichtman: ping? are you guys on vacation? ;) |
@alichtman: you seem to be the only active maintainer. Could you merge this straightforward, harmless patch? |
I'd ping @vladdoster. I haven't merged any real code to this ever, really. Don't have time / bandwidth to be a "good" maintainer |
Ping @vladdoster then. The patch is harmless, could you merge? |
@vladdoster: Hi. What holds you before merging this PR? |
I've removed the 11 unused entries from themes via this script: for col in `grep -o col-[[:alnum:]]* share/themes/blue.zsh `; do
if ! \ag ${col##col-}\} zinit*.zsh &>/dev/null; then print missentry $col;
read -q && \
if sed -r -i -e "s/[[:space:]]+${col}[[:space:]]+\\\$'[^']*'//g" share/themes/*.zsh
then
print replaced
fi
fi
done It's output is:
I think that the theming is a good idea because:
|
@vladdoster: I've did what you requested and all CI checks pass (except for docs, which I cannot generate because no docker), so could you merge? |
Why isn't this PR yet merged? Is it because of doubts of usability? If yes, then I tell you that once it's merged, you'll never look back on the old, unseparated (tabular data in |
@vladdoster: ping above comment |
@vladdoster: Could we please stop playing in a mouse and a cat, and merge this straightforward, harmless and cleanup patch? |
@vladdoster: We could easily add support for this neon theme with the pr merged: |
@vladdoster you seem active today. Why not merge this straightforward, harmless, cleanup patch? What is the reason? |
Description
I think that the theming potential behind
+zinit-message
should be used. All styles like{error}
,{warn}
(or the new{w}
that includesWarning:
prefix β cool idea π),{pname}
have their corresponding keys inZINIT
hash. I think that exporting the tabular hash data (2 columns with pairs of key/value) to a separate file is a good idea also from code cleanliness perspective.Related Issue(s)
I'm refreshing an older PR #445, done before the color data has been refactored by @vladdoster ,
Motivation and Context
The
+zinit-message
function has been created with theming in mind from the start. It only felt that the styles database should first grow a little before another themes would be added. Now it seems complete, so it's a good moment of adding some themes.The patch is very simple β it only moves the
ZINIT+=( β¦ β¦ )
assignment to a separate fileshare/themes/default.zsh
and then is duplicated toblue.zsh
andgold.zsh
and then the copies are altered to different styling. Nothing can brokeβ¦Usage examples
Default theme β no changes:
Plugin installation:
Wrong ice error:
New "Blue" theme:
Plugin installation:
Wrong ice error:
New "Gold" theme:
Plugin installation:
Wrong ice error:
How Has This Been Tested?
Like the
Usage examples
section.Types of changes
Checklist: