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
I've got this working, and it looks pretty cool. There's a problem though... if a file changes while a command is running a second instance of that command will fire up. Is there a way to handle that, either in make or watch-make?
Somewhat related to this... if you've been editing multiple files for a single change and you tell you editor to "Save All", there's going to be a race condition between the editor, watch-make and make itself. I think it'd be useful if there was some kind of timeout where watch-make wouldn't run the target until it hadn't received any new notifications for at least X amount of time.
The text was updated successfully, but these errors were encountered:
BTW, it looks like flock might be an option in the makefile, but that would still allow several (or at least 2) make runs to queue up. I think the right solution for this is a combination of the timeout I mentioned above, and not allowing multiple make commands to execute at the same time.
I've got this working, and it looks pretty cool. There's a problem though... if a file changes while a command is running a second instance of that command will fire up. Is there a way to handle that, either in make or watch-make?
Somewhat related to this... if you've been editing multiple files for a single change and you tell you editor to "Save All", there's going to be a race condition between the editor, watch-make and make itself. I think it'd be useful if there was some kind of timeout where watch-make wouldn't run the target until it hadn't received any new notifications for at least X amount of time.
The text was updated successfully, but these errors were encountered: