From b7c3f0d88ec5658a71185175bdb84777cfc1827b Mon Sep 17 00:00:00 2001 From: ko1N Date: Fri, 13 Sep 2019 14:41:18 +0200 Subject: [PATCH] Fixed documentation for unix shebang usage --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 5816d882..14fa85dd 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,7 @@ The following features are defined: ### Self-Executing Scripts -On UNIX systems, you can use `#!/usr/bin/env cargo eval --` as a shebang line in a Rust script. If the script file is executable, this will allow you to execute a script file directly. +On UNIX systems, you can use `#!/usr/bin/env -S cargo eval --` as a shebang line in a Rust script. If the script file is executable, this will allow you to execute a script file directly. If you are using Windows, you can associate the `.crs` extension (which is simply a renamed `.rs` file) with `cargo-eval`. This allows you to execute Rust scripts simply by naming them like any other executable or script. @@ -86,7 +86,7 @@ The output of Cargo will be hidden unless compilation fails, or takes longer tha - `now.crs` (code block manifest with UNIX shebang and `.crs` extension): ```rust - #!/usr/bin/env cargo eval -- + #!/usr/bin/env -S cargo eval -- //! This is a regular crate doc comment, but it also contains a partial //! Cargo manifest. Note the use of a *fenced* code block, and the //! `cargo` "language".