Should it run the command upon start up, before any files are modified? about cargo-watch HOT 12 CLOSED

Suggestion: Use Github's new "Add a reaction" feature for voting. Add a +1 (👍) to this comment to say "I would like this feature" and -1 (👎) to say "I would not like this feature"

from cargo-watch.

This is now done with the entirely new version 4.0.0! It will run the command upon starting by default, but you can disable the behaviour using --postpone.

from cargo-watch.

Used cargo watch run with a simple iron example server, and expected it to run the command.

Maybe it should be an optional thing or depend on the cargo command?

from cargo-watch.

I think I'm going to rebuild cargo watch to more in the model of remy's
nodemon, if you know of it, after I do Notify v3. This would include the
functionality requested in this ticket.

On Thu, 30 Jun 2016, 19:36 Robin Stocker [email protected] wrote:

Used cargo watch run with a simple iron
http://ironframework.io/doc/iron/ example server, and expected it to
run the command.

Maybe it should be an optional thing or depend on the cargo command?

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#37 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAJgi3Z3-9fQMromw_IX0ARbfF3D1YRUks5qQ3HsgaJpZM4Hxa-W
.

from cargo-watch.

👍 Going to do this. Don't have an ETA, but it's on the todolist.

from cargo-watch.

I'm of either mind on this, so I'll wait for community feedback too.

from cargo-watch.

Yes please.

On Tue, Mar 15, 2016, 4:41 PM Félix Saparelli [email protected]
wrote:

I'm of either mind on this, so I'll wait for community feedback too.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#37 (comment)

from cargo-watch.

Also comment with your use case if it is different from the top-post. I'd love to have more insight into why people would want one or the other.

from cargo-watch.

I'm all for this as I wanted to watch a server, so the first run before anything changes is definitely useful. One alternate thing is to allow pressing Enter to trigger a build, regardless of the state of files. I believe that guard allows something similar.

from cargo-watch.

Nodemon does it by typing rs then Enter, which guards against restarting inadvertently if an interactive program is watched, or if one likes to use blank lines to visually separate runs when doing verbose debugging. That's probably what I'll go with. I use nodemon all the time, it's a very useful tool — it is very much the vision for cargo watch.

Speaking of, as much as I'd like to keep users here, I have no illusion of being able to bring it to greatness any time soon, so if you happen to have npm/node installed and want a very good cargo-watch alternative, go with nodemon:

# With long options for clarity:
$ nodemon --ext rs,toml --exec 'cargo run' --watch src --watch test --watch examples

# Short options for brevity:
$ nodemon -e rs,toml -x 'cargo run' -w src -w test -w examples

That should have the requisite behaviour.

from cargo-watch.

For other people landing here, there's now also a nodemon-like tool written in Rust: https://github.com/mattgreen/watchexec/

$ watchexec --restart "cargo run"

Edit: Removed --run-initially

from cargo-watch.

Note that --run-initially is the default now, so you don't need to specify it.

from cargo-watch.