Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a semaphore #2

Open
decibel opened this issue Sep 24, 2016 · 1 comment
Open

Need a semaphore #2

decibel opened this issue Sep 24, 2016 · 1 comment

Comments

@decibel
Copy link

decibel commented Sep 24, 2016

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.

@decibel
Copy link
Author

decibel commented Sep 24, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant