The improvements discussed in #8 are great - we can now have a script reload be triggered by the output of another script, like bscp monitor, nmcli monitor or /usr/sbin/alsactl monitor. However, while bspc subscribe will output the current status immediately upon executing the command, the others (and probably many more) only ever output something when there is a change to be reported. This leads to a situation where my volume and wifi scripts are only triggered once I change the volume or toggle the wifi off and on again.
What would be nice is to have an option to tell Captain to run those scripts at least once at startup, to get the initial status to be displayed. Maybe this could even be standard behavior, alternatively it could be an option, like init = true.
Feature request
The improvements discussed in #8 are great - we can now have a script reload be triggered by the output of another script, like
bscp monitor,nmcli monitoror/usr/sbin/alsactl monitor. However, whilebspc subscribewill output the current status immediately upon executing the command, the others (and probably many more) only ever output something when there is a change to be reported. This leads to a situation where my volume and wifi scripts are only triggered once I change the volume or toggle the wifi off and on again.What would be nice is to have an option to tell Captain to run those scripts at least once at startup, to get the initial status to be displayed. Maybe this could even be standard behavior, alternatively it could be an option, like
init = true.