#cargo-command #cargo-build #cargo-clean #run-command #let #running #multiple

app cargo-do

A Cargo plugin that adds the ‘do’ subcommand to let you run multiple cargo commands by running e.g. cargo do clean, build

9 releases

Uses old Rust 2015

0.4.0 Mar 16, 2016
0.3.1 Sep 3, 2015
0.2.5 Apr 24, 2015

#533 in Cargo plugins

Download history 72/week @ 2024-11-16 17/week @ 2024-11-23 16/week @ 2024-11-30 40/week @ 2024-12-07 7/week @ 2024-12-14 8/week @ 2025-01-04 8/week @ 2025-01-11 11/week @ 2025-01-18 47/week @ 2025-01-25 50/week @ 2025-02-01 52/week @ 2025-02-08 71/week @ 2025-02-15 94/week @ 2025-02-22 77/week @ 2025-03-01

307 downloads per month

MIT/Apache

7KB
95 lines

Cargo Do

Build Status

Allows you to put multiple cargo commands on one line, e.g.

$ cargo do clean, update, build

Installation

I don't know if there is an "official" way to install Cargo subcommands, but the easiest way is to put the generated cargo-do binary in the same directory as cargo. So, if you are on a *nix system, you could do the following:

$ git clone https://github.com/pwoolcoc/cargo-do
$ cd cargo-do
$ cargo build
$ cp target/cargo-do $(dirname $(which cargo))/

Verify that it is correctly installed by checking that do is in the command list:

$ cargo --list | egrep "do$"
    do

Using commas in your commands

Since cargo-do uses commas to delimit commands, you have to be careful when trying to run a command with a comma in it.

For example, this command will not run properly:

$ cargo do update, build, bench --bench "why are there commas, here"

It will be treated as if you did this:

$ cargo update
$ cargo build
$ cargo bench --bench "why are there commas
$ cargo here"

Which is obviously not what you want.

Because of the magic of shell escaping, you have a couple choices on how to get around this:

$ cargo do bench --bench "why are there commas\, here"

or

$ cargo do bench --bench why are there commas \\, here

However you want to do it, cargo-do will not delimit commands on an escaped comma.

No runtime deps