Currently, it is possible to crash dwl-guile when expressions for e.g. keybindings spawn child processes. The current workaround is to use the dwl:shcmd binding. However, we should make sure that no expression is able to crash dwl-guile.
I reverted the change that executed actions in new threads since that introduced quite significant delays. Evaluations using dwl-guile -e "<exp" will still be executed in a new thread though.
Currently, it is possible to crash dwl-guile when expressions for e.g. keybindings spawn child processes. The current workaround is to use the
dwl:shcmd
binding. However, we should make sure that no expression is able to crash dwl-guile.