You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: