Waybar VS mako

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

So, using this github issue as a reference, I'm trying to make a wofi menu that appears when a bluetooth file transmission is sent to my PC from my phone (or any other device for that matter).

I currently use mako for the notifications. When I play Strategy Games (Mouse is all over the place) and a notifcation pops up, the mouse gets stuck on the notification message until I click it.

I use avizo as a volume indicator, mako for notifications generally.

I guess some standard notifications app like https://github.com/emersion/mako doesn't suffice, as it isn't related to a window?

mako is a Wayland notification daemon from one of the principal Sway/wlroots devs, and is currently provided with openSUSEway. It's pretty minimalist, but so are most things in the Sway/wlroots ecosystem.

It's a notification, I use mako: https://github.com/emersion/mako

Notifications: mako

Is there any way to force dbus to use a specific notification daemon? On one of my systems, I run both Plasma and Sway. The latter obviously doesn't have a notification system, so I'm using mako. As far as I can tell, mako automatically launches when a notification is fired, however this causes an issue with Plasma. Plasma seems to be shutting down its own notification daemon in favor of anything else that's running, and I'm not sure if there's a way to prevent it from doing that

I don’t use Thunderbird, but does it support using FreeDesktop notifications e.g. that would work with Mako? Some applications will fall back to their own windows if there’s no notification daemon running.