https://github.com/pwoolcoc/cargo-do

allows you to run multiple cargo commands in a row
https://github.com/pwoolcoc/cargo-do

Last synced: 9 days ago
JSON representation

allows you to run multiple cargo commands in a row

• Host: GitHub
• URL: https://github.com/pwoolcoc/cargo-do
• Owner: pwoolcoc
• License: apache-2.0
• Created: 2014-11-20T21:13:10.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2017-07-14T13:13:35.000Z (almost 7 years ago)
• Last Synced: 2024-06-04T21:14:28.016Z (25 days ago)
• Language: Rust
• Size: 17.6 KB
• Stars: 20
• Watchers: 4
• Forks: 6
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE-APACHE

Lists

• awesome-rust - pwoolcoc/cargo-do
• awesome-rust - pwoolcoc/cargo-do - do](https://crates.io/crates/cargo-do)] — run multiple cargo commands in a row (Development tools / Build system)

README

        
# Cargo Do

[![Build Status](https://travis-ci.org/pwoolcoc/cargo-do.svg?branch=master)](https://travis-ci.org/pwoolcoc/cargo-do)

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

```

$ cargo do clean, update, build

```

## Installation

```

cargo install cargo-do

```

### From Source

Build the `cargo-do` binary and put it 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.