Most ops are no-op on OSX although the result is 0

[rrichardson]

I just ran rustup update and cargo install cargo-wa

19:53 $ rustup show
Default host: x86_64-apple-darwin

installed toolchains
--------------------

stable-x86_64-apple-darwin
nightly-x86_64-apple-darwin (default)

active toolchain
----------------

nightly-x86_64-apple-darwin (default)
rustc 1.23.0-nightly (827cb0d61 2017-11-26)

19:54 $ rustup update stable
info: syncing channel updates for 'stable-x86_64-apple-darwin'

  stable-x86_64-apple-darwin unchanged - rustc 1.22.1 (05e2e1c41 2017-11-22)

19:52 $ ~/.cargo/bin/cargo-wa --version
cargo-wa 0.1.1

19:53 $ ~/.cargo/bin/cargo-wa wa setup

19:53 $ echo $?
0

19:55 $ ~/.cargo/bin/cargo-wa wa new foo

19:56 $ echo $?
0

[mgattozzi]

If I'm understanding this correctly none of the commands are running at all?

[rrichardson]

That seems to be the case. If I were on Linux I could provide some more in-depth analysis.. (strace, etc) I'm on a mac, so I'm researching how to figure out exactly what is happening.

[rrichardson]

I just cloned and built. When running in debug, the commands all execute successfully.

[Meralis40]

I have the same bug on Windows 10: when installing via cargo install cargo-wa, none of the commands works, but local builds are ok. Errors in arguments are correctly reported when running the installed version.

[jice-nospam]

Same for me on a freshly installed ubuntu 17.10. setup and new commands have no effects