s/cargo-script/rust-script

Author: fornwall

src/file_assoc.rs

@@ -59,7 +59,7 @@ pub fn install_file_association() -> Result<()> {
         }
     }
 
-    println!("Created run-cargo-script registry entry.");
+    println!("Created rust-script registry entry.");
     println!("- Handler set to: {}", rcs_path);
 
     let hklm = RegKey::predef(wre::HKEY_LOCAL_MACHINE);
@@ -99,7 +99,7 @@ pub fn uninstall_file_association() -> Result<()> {
     if ignored_missing {
         println!("Ignored some missing registry entries.");
     }
-    println!("Deleted run-cargo-script registry entry.");
+    println!("Deleted rust-script registry entry.");
 
     {
         let hklm = RegKey::predef(wre::HKEY_LOCAL_MACHINE);

src/main.rs

@@ -1,14 +1,3 @@
-/*!
-`cargo-script` is a Cargo subcommand designed to let people quickly and easily run Rust "scripts" which can make use of Cargo's package ecosystem.
-
-Or, to put it in other words, it lets you write useful, but small, Rust programs without having to create a new directory and faff about with `Cargo.toml`.
-
-As such, `cargo-script` does two major things:
-
-1. Given a script, it extracts the embedded Cargo manifest and merges it with some sensible defaults.  This manifest, along with the source code, is written to a fresh Cargo package on-disk.
-
-2. It caches the generated and compiled packages, regenerating them only if the script or its metadata have changed.
-*/
 #![forbid(unsafe_code)]
 extern crate env_logger;
 #[macro_use]

src/manifest.rs

@@ -1,5 +1,5 @@
 /*!
-This module is concerned with how `cargo-script` extracts the manfiest from a script file.
+This module is concerned with how `rust-script` extracts the manfiest from a script file.
 */
 extern crate pulldown_cmark;
 extern crate regex;
@@ -307,7 +307,7 @@ fn test_strip_hashbang() {
     assert_eq!(
         strip_hashbang(
             "\
-#!/usr/bin/env run-cargo-script
+#!/usr/bin/env rust-script
 and the rest
 \
         "

src/platform.rs

@@ -83,9 +83,9 @@ mod inner {
     }
 
     /**
-    Returns `true` if `cargo-script` should force Cargo to use coloured output.
+    Returns `true` if `rust-script` should force Cargo to use coloured output.
 
-    This depends on whether `cargo-script`'s STDERR is connected to a TTY or not.
+    This depends on whether `rust-script`'s STDERR is connected to a TTY or not.
     */
     pub fn force_cargo_color() -> bool {
         atty::is(atty::Stream::Stderr)
@@ -147,7 +147,7 @@ pub mod inner {
     }
 
     /**
-    Returns `true` if `cargo-script` should force Cargo to use coloured output.
+    Returns `true` if `rust-script` should force Cargo to use coloured output.
 
     Always returns `false` on Windows because colour is communicated over a side-channel.
     */