From 66be8debbf34b82a735b17c09ff400d30d8a48f1 Mon Sep 17 00:00:00 2001 From: "Henry J. Webster" Date: Mon, 3 Aug 2026 17:32:56 -0500 Subject: enzo/yambar: add niri + jq to service PATH The new yambar niri-workspaces.sh script runs `niri msg --json` piped to jq, and the workspace on-clicks run `niri msg action focus-workspace`. yambar spawns these via execvp with no shell, so both binaries must be on the service PATH alongside the existing libnotify/wireplumber. Assisted-by: Claude Code:claude-opus-4-8 --- machines/enzo/desktop.nix | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'machines/enzo/desktop.nix') diff --git a/machines/enzo/desktop.nix b/machines/enzo/desktop.nix index 6599f45..59204b4 100644 --- a/machines/enzo/desktop.nix +++ b/machines/enzo/desktop.nix @@ -62,9 +62,11 @@ after = [ "graphical-session.target" ]; # yambar runs on-click commands via execvp with no shell, so their # binaries must be on the service PATH. libnotify -> notify-send, - # wireplumber -> wpctl (volume). Without this every on-click fails with + # wireplumber -> wpctl (volume), niri -> niri msg (workspace module + + # its focus-workspace on-clicks), jq -> parses niri's --json output in + # niri-workspaces.sh. Without this every on-click/script fails with # ENOENT ("No such file or directory"). - path = [ pkgs.libnotify pkgs.wireplumber ]; + path = [ pkgs.libnotify pkgs.wireplumber pkgs.niri pkgs.jq ]; serviceConfig = { ExecStart = "${pkgs.yambar}/bin/yambar"; Restart = "on-failure"; -- cgit v1.3