Tom Willemse a0034e7659 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.		2022-04-20 17:24:05 -07:00
..
cmst.scm	Add cmst and kdeconnect configurations	2022-04-19 01:14:14 -07:00
compton.scm	Use forkexec instead of system constructor for picom	2022-04-20 17:24:05 -07:00
herbstluftwm.scm	Switch to the first tag before deleting the default tag	2022-04-19 01:16:11 -07:00
kdeconnect.scm	Add cmst and kdeconnect configurations	2022-04-19 01:14:14 -07:00
kitty.scm	Install kitty when the kitty service is used	2022-04-05 00:54:09 -07:00
polybar.scm	Add basic polybar configuration	2022-04-16 00:24:34 -07:00
syncthing.scm	Use forkexec, not system, constructor for syncthing	2022-04-20 17:17:57 -07:00
xbindkeys.scm	Call the ‘first-binding’ function for xbindkeys	2022-04-20 16:45:04 -07:00
xdisorg.scm	Support symbols with special characters in configuration group keys	2022-04-02 01:35:20 -07:00
xmodmap.scm	Use shepherd to start xmodmap rather than on first startup	2022-04-12 21:33:15 -07:00
xsession.scm	Centralize definition of ‘mixed-executable-file’	2022-04-15 22:13:33 -07:00
zsh.scm	Ensure packages are installed for the zsh plugins	2022-04-11 23:44:19 -07:00