cargo-open
cargo-open copied to clipboard
A third-party cargo extension to allow you to open a dependent crate in your $EDITOR
``` $ cargo install cargo-open Updating registry `https://github.com/rust-lang/crates.io-index` Downloading cargo-open v0.3.0 Downloading clap v2.19.1 Downloading rustc-serialize v0.3.22 Downloading num_cpus v1.2.0 Downloading libc v0.2.18 Downloading tar v0.4.9 Downloading gcc v0.3.39 Downloading...
When used with `sudo` it works. Other cargo plugins install without sudo. I can't see why sudo should be necessary. Without sudo I get: ``` $ cargo install cargo-open --verbose...
This PR improves the error handling in this subcommand. It was necessary to pin the `cargo` dependency to have certain functionality available on the stable release. With this errors do...
**DO NOT MERGE** This small change allows running `cargo-open` standalone _as well as_ as a subcommand of `cargo`...well, _almost_. Running `cargo open ` works as expected. Running `cargo-open ` also...
In `main.rs`, add a unit test for the `cargo_dir` function that checks that it panics if we have specified a new crate in the `Cargo.toml` file but have not yet...
In `main.rs`, add unit tests for the `cargo_dir` function that checks that it returns the correct directory for different kinds of crates that have been installed, like: - A crate...
In `main.rs`, add a unit test for the `cargo_dir` function that checks that it panics if we try to run this command in a directory that doesn't have a `Cargo.toml`...
In `main.rs`, add a unit test for the `cargo_dir` function that checks that it panics if we have specified a new crate in the `Cargo.toml` file but have not yet...
In `main.rs`, add a unit test for the `cargo_dir` function that checks that it returns the correct source code directory for a crate that is a dependency of a crate...
Since `std::process::Command` expects a program, and only a program, in `Command::new`. I don't really want to have to parse args out of $EDITOR myself, it'd be nice if there was...