At the moment the watch command immediatly triggers registered actions.
But often there is a change followed by a small change after that, therefore the actions run often twice for me.
It should be possible to define a waiting time for the watch command so that it does not run of immediatly but waits. This waiting time should reset after a new event, so that it does not run, while there are still frequent changes to files.
At the moment the watch command immediatly triggers registered actions.
But often there is a change followed by a small change after that, therefore the actions run often twice for me.
It should be possible to define a waiting time for the watch command so that it does not run of immediatly but waits. This waiting time should reset after a new event, so that it does not run, while there are still frequent changes to files.