-
-
Notifications
You must be signed in to change notification settings - Fork 690
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
watchmedo auto-restart behavior change with 2.1.9 #922
Comments
This seems like it would be very simple to implement with a script, which would run the tools once initially and then call BTW, this seems like a great use-case for grouping together multiple events happening in a short time-frame ("debouncing") and launching the command only after that, similar to #542. This was implemented for |
Running the tools once initially and then calling Could we get a flag to disable (or enable, depending on what you want as the default) the following two lines?
|
@BoboTiG WDYT? We could add a flag for the trick and the CLI command. |
@taleinat yup, that would be a simple solution 👍 |
Thanks a lot @taleinat ! I'll see to cut a new release in the week. |
v2.3.0 is out 🍾 |
We were using
watchmedo auto-restart
to call mypy and some flake8 tooling upon file changes. With the changes introduced by #896, these processes re-run continually every time they exit whereas before they were re-ran upon a watched file/directory change.The name
auto-restart
makes me believe that this is actually desirable behavior and perhaps we were misusing that sub-command, however there doesn't appear to be an alternative to get the behavior we once had.watchmedo shell-command
only runs the command on change with no option to run it once and also upon watched file change.Is there a way to add a flag to
auto-restart
which only restarts on an exit code, or maybe a way to useshell-command
to call the command initially and then repeat on a file change?The text was updated successfully, but these errors were encountered: