ryuslash/dotfiles
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Use forkexec instead of system constructor for picom

Browse source 
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.
This commit is contained in:
Tom Willemse 2022-04-20 17:24:05 -07:00
parent 211bfcb544
commit a0034e7659
1 changed files with 4 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
oni/home/services/compton.scm
View file

@ -97,11 +97,10 @@
;(requirement '(xorg-server)) ;(requirement '(xorg-server))
(auto-start? #t) (auto-start? #t)
(start (start
#~(make-system-constructor #~(make-forkexec-constructor
(string-join (list #$(file-append (home-picom-configuration-package config) "/bin/picom")
(list #$(file-append (home-picom-configuration-package config) "/bin/picom") "--config" #$(home-picom-config-file config))
"--config" #$(home-picom-config-file config) #:log-file (format #f "~a/.local/var/log/picom.log" (getenv "HOME"))))
"-b"))))
(stop #~(make-kill-destructor))))) (stop #~(make-kill-destructor)))))
(define (home-picom-extension old-config extension-configs) (define (home-picom-extension old-config extension-configs)