Stop tracking wallust output
The work laptop's first install left five files dirty, all of them wallust targets. Tracking generated colour files means each machine rewrites the others' palette on every theme change — exactly the churn a shared repo should not have. hypr, waybar and swaync now get their colours as real files written into real directories, so nothing is linked and nothing is tracked. kitty and qutebrowser land inside directories this repo links wholesale, so those two are ignored by path instead. swaync switched from a directory link to two file links to make room for its generated colors.css. Regeneration is automatic: hypr_refresh runs every 15 seconds on both laptops, so a fresh machine has colours within a quarter of a minute.
This commit is contained in:
1 parent
7e95a41f33
commit
9fc991a245
11 files changed
+10
-168
No files matched your search
@@ -1,15 +0,0 @@
|
||||
# Hyprland with colors from wallust
|
||||
# The
|
||||
# You can use this template by adding the following to wallust.toml:
|
||||
# hypr = { src = "hyprland-colors.conf", dst = "~/.config/hypr/colors.conf" }
|
||||
# and then on hyprland.conf:
|
||||
# source = ~/.config/hypr/colors.conf
|
||||
|
||||
general {
|
||||
# Here we use `saturate` filter to have more vibrant colors,
|
||||
# not matter the scheme, since the border should seek the attention
|
||||
col.active_border = rgb(357EBD) rgb(B66F37) rgb(B57638) rgb(BA8234) rgb(C4823A) rgb(DD9B43)
|
||||
# color0 is almost the same as the background color,
|
||||
# by putting ee as the alpha, it makes it 100% transparent
|
||||
col.inactive_border = rgba(3B3A39ee)
|
||||
}
|
||||
Reference in new issue
Block a user