--- source: cli/tests/help.rs expression: String::from_utf8(output.stdout).unwrap() --- watchexec 1.17.1 Execute commands when watched files change USAGE: watchexec.exe [FLAGS] [OPTIONS] ... FLAGS: --changes-only Only print path change information. Overridden by --verbose -c, --clear Clear screen before executing command -h, --help Prints help information --no-default-ignore Skip auto-ignoring of commonly ignored globs --no-environment Do not set WATCHEXEC_*_PATH environment variables for the command --no-ignore Skip auto-loading of ignore files (.gitignore, .ignore, etc.) for filtering --no-meta Ignore metadata changes --no-process-group Do not use a process group when running the command -n, --no-shell Do not wrap command in a shell. Deprecated: use --shell=none instead. --no-vcs-ignore Skip auto-loading of .gitignore files for filtering -N, --notify Send a desktop notification when watchexec notices a change (experimental, behaviour may change) -p, --postpone Wait until first change to execute command --print-events Print events that trigger actions -r, --restart Restart the process if it's still running. Shorthand for --on-busy-update=restart -V, --version Prints version information -v, --verbose Print debugging messages (-v, -vv, -vvv; use -vvv for bug reports) -W, --watch-when-idle Deprecated alias for --on-busy-update=do-nothing, which will become the default in 2.0. OPTIONS: -d, --debounce Set the timeout between detected change and command execution, defaults to 100ms -e, --exts Comma-separated list of file extensions to watch (e.g. js,css,html) -f, --filter ... Ignore all modifications except those matching the pattern -i, --ignore ... Ignore modifications to paths matching the pattern --on-busy-update Select the behaviour to use when receiving events while the command is running. Current default is queue, will change to do-nothing in 2.0. [possible values: do-nothing, queue, restart, signal] -w, --watch ... Watch a specific file or directory --force-poll Force polling mode (interval in milliseconds) --shell Use a different shell, or `none`. Try --shell=powershell, which will become the default in 2.0. ARGS: ... Command to execute Use @argfile as first argument to load arguments from the file `argfile` (one argument per line) which will be inserted in place of the @argfile (further arguments on the CLI will override or add onto those in the file).