This was fine when using clap 2.20.5. However, since updating to 2.21 (or above), I've started getting the following:

$ cargo multi fmt -- --write-mode=diff
-------------------------------------
Executing cargo fmt --write-mode=diff
-------------------------------------

crate1:
Unrecognized option: 'write-mode'.
usage: cargo fmt [options]

Options:
    -h, --help          show this message
    -q, --quiet         no output printed to stdout
    -v, --verbose       use verbose output
    -p, --package <package>
                        specify package to format (only usable in workspaces)
        --all           format all packages (only usable in workspaces)

This utility formats all bin and lib files of the current crate using rustfmt. Arguments after `--` are passed to rustfmt.

crate2:
Unrecognized option: 'write-mode'.
usage: cargo fmt [options]
...

Something has changed with the way clap handles arguments: it seems to silently swallow any number of bare --s. I'm not sure why this is, though.

Alternatively, pinning to a known-good version would suffice (`"~2.20.0").

https://gitlab.com/imp/cargo-multi gives me a 404, that's also the only place linked to from https://crates.io/crates/cargo-multi so if it's gone for good it would be nice to update the links there.

This adds the manifest path option to commands run, this ensures that all warnings are relative to the current directory, rather than having warnings about main.rs and being unable to determine which crate has the warning was present in.

This pull request add the ability for cargo multi to run the cargo commands across any crates in the workspace members section of a Cargo.toml file in the current directory, if there are none then it just reverts to the old behavior. I have also added that the first error code reported gets returned by cargo multi to make it easier for scripts using cargo multi.

Hi,

this looks like a great tool to do multi-crate publishing. What I mean: I have a project where a lot of crates live within the same repository (imag). All of these crates depend on each other (well, it is a tree-ish structure, not a circle of course). I released my first version (0.2.0) some days ago. I did it with this script:

while true; do 
   for dir in *; pushd "$dir"; cargo publish; popd; done
done

(not exactly that script, but you get the gist of it)

Another possibility would be to manually find the dependency tree and do it by hand. Or, and that's what I'm suggesting: using a tool for it which internally gets the dependency tree of all crates to work on and cargo publish them in the right order.

TL;DR: allow me to cargo multi publish a set of crates that might depend on eachother and optimize this process to publish them in the right order (so, crates at the root of the dependency tree first, others later).