dotfiles VS Waybar

I'm using make to manage the symlinks and a few other things, with git ofc. (https://github.com/LoricAndre/dotfiles if you wanna check it out)

Be careful though, they include my config for around 20 plugins, shifting hjkl to jklm on azerty keyboard etc. : https://github.com/LoricAndre/dotfiles. The files you migt be interested in are mostly in nvim, nvim/lua and nvim/lua/plugins.

I'm using bitwarden, and it has an official cli client that I've extended in my dotfiles to integrate fzf, you'll just need to adjust the commands for interacting with your clipboard : https://github.com/LoricAndre/dotfiles/blob/main/bin/fbw. Once you've installed the cli client, you need to login and then you can start the script, it will prompt you for an url match, then username if there are multiple accounts for that url, then put the username in the primary clipboard and the password in the system clipboard.

You can check out my dotfiles and adapt them : I'm using makefiles and perl to add colors to all my config files : https://github.com/LoricAndre/dotfiles

I've pretty much always used nerd fonts. For the config, as I don't care about anything other than monospace, it all fits in one file, ~/.config/fontconfig/conf.d/99-monospace.conf. the file

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