Merge pull request #398 from BO41/prefix

Remove $ prefix from bash snippets

Author: pietroalbini

posts/2015-10-29-Rust-1.4.md

@@ -77,8 +77,8 @@ Finally, one major Cargo improvement: [`cargo update` will now print extra
 information about what it is
 changing.](https://github.com/rust-lang/cargo/pull/1931) For example:
 
-```text
-$ cargo update
+```console
+cargo update
     Updating registry `https://github.com/rust-lang/crates.io-index`
     Updating libc v0.1.8 -> v0.1.10
     Updating memchr v0.1.3 -> v0.1.5

posts/2016-05-05-cargo-pillars.md

@@ -157,8 +157,8 @@ edit the `Cargo.toml` and add the `time` crate from [crates.io](https://crates.i
 Now that we've added the `time` crate, let's see what happens if we ask Cargo to
 build our package:
 
-```
-$ cargo build
+```console
+cargo build
    Compiling winapi v0.2.6
    Compiling libc v0.2.10
    Compiling winapi-build v0.1.1
@@ -173,16 +173,15 @@ up into smaller crates that do one thing and do it well**.
 
 Now that we successfully built our crate, what happens if we try to build it again?
 
-```
-$ cargo build
-
+```console
+cargo build
 ```
 
 Nothing happened at all. Why's that? We can always ask Cargo to give us more
 information through the `--verbose` flag, so let's do that:
 
-```
-$ cargo build --verbose
+```console
+cargo build --verbose
        Fresh libc v0.2.10
        Fresh winapi v0.2.6
        Fresh winapi-build v0.1.1
@@ -240,8 +239,8 @@ left off, with the exact same source code for all of our dependencies.
 To do this, we check in our `Cargo.lock` and clone the repository on our new
 machine. Then, we run `cargo build` again.
 
-```
-$ cargo build
+```console
+cargo build
    Compiling libc v0.2.10
    Compiling winapi v0.2.6
    Compiling winapi-build v0.1.1
@@ -271,8 +270,8 @@ fn main() {
 
 To run the example, we ask Cargo to build and run it:
 
-```
-$ cargo run --example date
+```console
+cargo run --example date
    Compiling datetime v0.1.0 (file:///Users/ykatz/Code/datetime)
      Running `target/debug/examples/date`
 26 Apr 2016 :: 05:03:38
@@ -322,8 +321,8 @@ to our package:
 
 After using the crate in our library, let's run `cargo build` again:
 
-```
-$ cargo build
+```console
+cargo build
     Updating registry `https://github.com/rust-lang/crates.io-index`
  Downloading tz v0.2.1
  Downloading byteorder v0.5.1
@@ -386,8 +385,8 @@ fn bench_date(b: &mut Bencher) {
 ```
 If we then run `cargo bench`:
 
-```
-$ cargo bench
+```console
+cargo bench
    Compiling winapi v0.2.6
    Compiling libc v0.2.10
    Compiling byteorder v0.5.1
@@ -450,8 +449,8 @@ library for Unix-specific functionality.
 
 As before, when I run `cargo build`, Cargo *conservatively* adds `nix` and its dependencies:
 
-```
-$ cargo build
+```console
+cargo build
     Updating registry `https://github.com/rust-lang/crates.io-index`
  Downloading nix v0.5.0
  Downloading bitflags v0.4.0

posts/2016-05-13-rustup.md

@@ -144,8 +144,8 @@ stable toolchain that targets the 64-bit, MSVC ABI.
 
 [abi]: https://www.rust-lang.org/downloads.html#win-foot
 
-```
-$ rustup default stable-x86_64-pc-windows-msvc
+```console
+rustup default stable-x86_64-pc-windows-msvc
 info: syncing channel updates for 'stable-x86_64-pc-windows-msvc'
 info: downloading component 'rustc'
 info: downloading component 'rust-std'

posts/2016-08-10-Shape-of-errors-to-come.md

@@ -94,8 +94,8 @@ explanations.
 Today, when you can call `--explain`, you pass an error code. The compiler then prints out
 an extended message that goes into more detail about how errors of that form occur:
 
-```
-> rustc --explain E0200
+```console
+rustc --explain E0200
 
 Unsafe traits must have unsafe implementations. This error occurs when an
 implementation for an unsafe trait isn't marked as unsafe. This may be resolved

posts/2016-09-08-incremental.md

@@ -28,7 +28,7 @@ time since implementation started towards the end of last year, all of the
 [basic components][incr-comp-rfc] are in place, the bulk of the groundwork has
 been done. You can give it a try in the nightly version of the compiler:
 
-```
+```console
 rustc -Zincremental=<path> ./main.rs
 ```
 

posts/2016-09-29-Rust-1.12.md

@@ -73,7 +73,7 @@ we showed above, at the start of the post? Here's an example of attempting to
 compile that code while passing the `--error-format=json` flag:
 
 ```bash
-$ rustc borrowck-assign-comp.rs --error-format=json
+rustc borrowck-assign-comp.rs --error-format=json
 {"message":"cannot assign to `p.x` because it is borrowed","level":"error","spans":[{"file_name":"borrowck-assign-comp.rs","byte_start":562,"byte_end":563,"line_start":15,"line_end":15,"column_start":14,"column_end":15,"is_primary":false,"text":[{"text":"    let q = &p;","highlight_start":14,"highlight_end":15}],"label":"borrow of `p.x` occurs here","suggested_replacement":null,"expansion":null}],"label":"assignment to borrowed `p.x` occurs here","suggested_replacement":null,"expansion":null}],"children":[],"rendered":null}
 {"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":null}
 ```
@@ -117,7 +117,7 @@ and easier to verify that they are correct.
 * [The compiler can now be built against LLVM 3.9](https://github.com/rust-lang/rust/pull/35594)
 * [Test binaries now support a `--test-threads` argument to specify the number
   of threads used to run tests, and which acts the same as the
-  `RUST_TEST_THREADS` environment variable](https://github.com/rust-lang/rust/pull/35414)  
+  `RUST_TEST_THREADS` environment variable](https://github.com/rust-lang/rust/pull/35414)
 * [The test runner now emits a warning when tests run over 60
   seconds](https://github.com/rust-lang/rust/pull/35405)
 * [Rust releases now come with source packages that can be installed by rustup

posts/2016-12-22-Rust-1.14.md

@@ -42,7 +42,7 @@ small taste of how it works, once you have [emscripten] installed, compiling
 some Rust code to WebAssembly is as easy as:
 
 ```bash
-$ rustup target add wasm32-unknown-emscripten
+rustup target add wasm32-unknown-emscripten
 $ echo 'fn main() { println!("Hello, Emscripten!"); }' > hello.rs
 $ rustc --target=wasm32-unknown-emscripten hello.rs
 $ node hello.js

posts/2017-02-02-Rust-1.15.md

@@ -10,7 +10,7 @@ systems programming language focused on safety, speed, and concurrency.
 If you have a previous version of Rust installed, getting Rust 1.15 is as easy as:
 
 ```bash
-$ rustup update stable
+rustup update stable
 ```
 
 If you don't have it already, you can [get `rustup`][install] from the

posts/2017-02-09-Rust-1.15.1.md

@@ -10,7 +10,7 @@ systems programming language focused on safety, speed, and concurrency.
 If you have a previous version of Rust installed, getting Rust 1.15.1 is as easy as:
 
 ```bash
-$ rustup update stable
+rustup update stable
 ```
 
 If you don't have it already, you can [download Rust][install] from the

posts/2017-03-16-Rust-1.16.md

@@ -10,7 +10,7 @@ systems programming language focused on safety, speed, and concurrency.
 If you have a previous version of Rust installed, getting Rust 1.16 is as easy as:
 
 ```bash
-$ rustup update stable
+rustup update stable
 ```
 
 If you don't have it already, you can [get `rustup`][install] from the
@@ -114,7 +114,7 @@ will live as long as `Name`, which is required for `Name` to be valid. Let's try
 code with Rust 1.15.1:
 
 ```bash
-> rustc +1.15.1 foo.rs --crate-type=lib
+rustc +1.15.1 foo.rs --crate-type=lib
 error[E0495]: cannot infer an appropriate lifetime for lifetime parameter in generic type due to conflicting requirements
   --> .\foo.rs:10:5
    |
@@ -138,7 +138,7 @@ The compiler explains the issue, and gives a helpful suggestion. So let's try it
 the `'a`, and compile again:
 
 ```bash
-> rustc +1.15.1 .\foo.rs --crate-type=lib
+rustc +1.15.1 .\foo.rs --crate-type=lib
 error[E0308]: method not compatible with trait
   --> .\foo.rs:10:5
    |
@@ -163,7 +163,7 @@ It still doesn't work. That help message was not actually helpful. It does sugge
 lifetime, this time on `Name`. If we do that...
 
 ```bash
-> rustc +1.15.1 .\foo.rs --crate-type=lib
+rustc +1.15.1 .\foo.rs --crate-type=lib
 <snip>
 help: consider using an explicit lifetime parameter as shown: fn from_str(s: &'a str) -> Result<Name<'a>, ()>
   --> .\foo.rs:10:5
@@ -175,7 +175,7 @@ This diagnostic was well-intentioned, but when it's wrong, it was *very* wrong,
 it wouldn't even suggest valid Rust syntax! Furthermore, more advanced Rust users didn't really need the
 suggestion, but new Rustaceans would take them to heart, and then be led down this bad path. As such, we decided
 that for now, [we should remove the help message entirely]. We may bring it back in the future, but only if we can
-limit false positives. 
+limit false positives.
 
 [we should remove the help message entirely]: https://github.com/rust-lang/rust/pull/37057