flavours VS Waybar

You might be interested in this base16 helper tool: https://github.com/Misterio77/flavours

https://github.com/Misterio77/flavours lets you manage base16 themes. The concept is pretty simple; you just add comments to your dot files and this script inserts your color scheme when you call it. It has saved me a lot of time!

I like https://github.com/Misterio77/flavours with any of the config files for GTK, terminal (many popular ones) and whatever else you want to theme including xresources and polybar. The key for me coloring i3 was using xresources as I can theme almost everything like Spotify and rofi from one file. Except dunst which is annoying but easy to config. Like spicetify has an xresources theme.

Hello everyone, I installed Misterio77/flavours from aur but I get errors every time I try to use it.

I use flavours, it generates config files for base16 colourschemes.

There are also these. They can, additionally, be invoked with other apps or scripts out there. (I use flavours).

So I found this project on this subreddit (https://github.com/Misterio77/flavours), and after a bit of configuration for my tools, I was able to generate this beautiful colorscheme from the Macos Monterey wallpaper.

Flavours works quite well for this.

Colors: Generated with Flavours

If I understand https://github.com/Alexays/Waybar/wiki/Configuration correctly, what is to be displayed is defined in a JSON file that can be located in one of the directories mentioned.

GNU calls their extensions "equivalent to" things I'd have suggested trying ($_I or $-l), but I'm not sure if the equivalents are themselves GNU extensions, too. Regardless, reading this Waybar Github issue about %OI, I get the impression there was a regression at some point, in any case on March 27th 2022 someone says it "used to work fine until recently".

hope it helps. source btw: https://github.com/Alexays/Waybar/issues/2177

{ config, pkgs, ... }: { wayland.windowManager.sway = let patchedWaybar = pkgs.waybar.overrideAttrs(prev: final: { patches = [ (pkgs.fetchpatch { url = "https://github.com/Alexays/Waybar/pull/2134.diff"; sha256 = "1hzdv3b8zzps50pdcb8pj9cxwaix4q2d4gsqb9dl9vflgl429hq3"; }) ]; }); in { enable = true; config.bars = [{ statusCommand = "${patchedWaybar}/bin/waybar"; }]; };

See this issue. CSS and only new properties in config are reloaded when SIGUSR2 is triggered.

I think this has just been added to waybar (wlr/workspaces) to work in a similar manner to how it is in sway/workspaces. No need for fake empty terminals. Something was merged for wwlr/workspaces in the waybar github. See - https://github.com/Alexays/Waybar/pull/2089.

Ah, well in looking at their git, it appears some do have fallback font issues. See here - https://github.com/Alexays/Waybar/issues/215