From a0034e7659a957997a58b7495abad8e6788f80ad Mon Sep 17 00:00:00 2001
From: Tom Willemse
Date: Wed, 20 Apr 2022 17:24:05 -0700
Subject: Use forkexec instead of system constructor for picom

The example was using a system constructor with a kill destructor, but I don't
think those two work together. I prefer having the application run in the
foreground and using the shepherd way of forking so I have more control.
---
 oni/home/services/compton.scm | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

(limited to 'oni')

diff --git a/oni/home/services/compton.scm b/oni/home/services/compton.scm
index 6e354fa..a1aedf6 100644
--- a/oni/home/services/compton.scm
+++ b/oni/home/services/compton.scm
@@ -97,11 +97,10 @@
       ;(requirement '(xorg-server))
       (auto-start? #t)
       (start
-       #~(make-system-constructor
-          (string-join
-            (list #$(file-append (home-picom-configuration-package config) "/bin/picom")
-                  "--config" #$(home-picom-config-file config)
-                  "-b"))))
+       #~(make-forkexec-constructor
+          (list #$(file-append (home-picom-configuration-package config) "/bin/picom")
+                "--config" #$(home-picom-config-file config))
+          #:log-file (format #f "~a/.local/var/log/picom.log" (getenv "HOME"))))
       (stop #~(make-kill-destructor)))))
 
 (define (home-picom-extension old-config extension-configs)
-- 
cgit v1.2.3-54-g00ecf