Remove leading $ for shell commands to be consistent with the website

* This also makes it much easier to copy-paste the commands.
* Keep it when a snippet mixes command line and output.

Author: eregon

doc/contributor/benchmarking.md

@@ -5,9 +5,9 @@
 First build TruffleRuby and include the GraalVM Compiler:
 
 ```bash
-$ jt build --env native
+jt build --env native
 # or
-$ jt build --env jvm-ce
+jt build --env jvm-ce
 ```
 
 See [The "Building" section of the Contributor Workflow document](workflow.md#Building) for details on the different
@@ -17,9 +17,9 @@ that performs JIT compilation for Ruby, though that can of course be benchmarked
 Then run the benchmark, for instance:
 
 ```bash
-$ jt --use native benchmark bench/classic/mandelbrot.rb --simple
+jt --use native benchmark bench/classic/mandelbrot.rb --simple
 # or
-$ jt --use jvm-ce benchmark bench/classic/mandelbrot.rb --simple
+jt --use jvm-ce benchmark bench/classic/mandelbrot.rb --simple
 ```
 
 Output is iterations per second, printed roughly every second (more frequently
@@ -34,9 +34,9 @@ minimal dependencies, which can be useful to debug or tune performance.
 Run the fixed-workload harness with minimal dependencies with:
 
 ```bash
-$ jt --use native ruby bench/optcarrot/fixed-workload.rb
+jt --use native ruby bench/optcarrot/fixed-workload.rb
 # or
-$ jt --use jvm-ce ruby bench/optcarrot/fixed-workload.rb
+jt --use jvm-ce ruby bench/optcarrot/fixed-workload.rb
 ```
 
 # Benchmarking Other Implementations
@@ -45,6 +45,6 @@ You can benchmark an entirely different implementation using the `--use` option
 or with the `RUBY_BIN` environment variable.
 
 ```bash
-$ jt --use ruby benchmark bench/classic/mandelbrot.rb --simple
-$ RUBY_BIN=ruby jt benchmark bench/classic/mandelbrot.rb --simple
+jt --use ruby benchmark bench/classic/mandelbrot.rb --simple
+RUBY_BIN=ruby jt benchmark bench/classic/mandelbrot.rb --simple
 ```

doc/contributor/cexts.md

@@ -6,12 +6,12 @@ There are various ways to test C extensions.
 Here is a list going from testing single functions to testing Bundler.
 
 ```bash
-$ jt test :capi
-$ jt test :truffle_capi
-$ jt test :library_cext
-$ jt test mri --all-sulong
-$ jt test cexts
-$ jt test bundle
+jt test :capi
+jt test :truffle_capi
+jt test :library_cext
+jt test mri --all-sulong
+jt test cexts
+jt test bundle
 ```
 
 Note: the last 2 currently require the gem test pack.
@@ -29,7 +29,7 @@ jt cextc bench/chunky_png/oily_png
 Then follow the instructions for benchmarking above, and then try:
 
 ```bash
-$ USE_CEXTS=true TRUFFLERUBYOPT="--experimental-options --cexts-log-load" jt benchmark bench/chunky_png/chunky-color-r.rb --simple
+USE_CEXTS=true TRUFFLERUBYOPT="--experimental-options --cexts-log-load" jt benchmark bench/chunky_png/chunky-color-r.rb --simple
 ```
 
 These benchmarks have Ruby fallbacks, so we should carefully check that the

doc/contributor/docker.md

@@ -16,10 +16,10 @@ built to use TruffleRuby.
 For example, to run a full set of tests on a set of new release candidate tarballs:
 
 ```bash
-$ jt docker test --graalvm graalvm-ce.tar.gz llvm-toolchain-installable.jar:ruby-installable-ce.jar --test release_branch
-$ jt docker test --graalvm graalvm-ee.tar.gz llvm-toolchain-installable.jar:ruby-installable-ee.jar --test release_branch
-$ jt docker test --graalvm graalvm-ee.tar.gz llvm-toolchain-installable.jar:ruby-installable-ee.jar --rebuild-images native-image-installable-ee.jar --test release_branch
-$ jt docker test --standalone truffleruby-linux-amd64.tar.gz --test release_branch
+jt docker test --graalvm graalvm-ce.tar.gz llvm-toolchain-installable.jar:ruby-installable-ce.jar --test release_branch
+jt docker test --graalvm graalvm-ee.tar.gz llvm-toolchain-installable.jar:ruby-installable-ee.jar --test release_branch
+jt docker test --graalvm graalvm-ee.tar.gz llvm-toolchain-installable.jar:ruby-installable-ee.jar --rebuild-images native-image-installable-ee.jar --test release_branch
+jt docker test --standalone truffleruby-linux-amd64.tar.gz --test release_branch
 ```
 
 ## Distributions
@@ -62,7 +62,7 @@ as repository URLs being cached that become unavailable). Therefore we recommend
 regularly clearing your Docker cache.
 
 ```bash
-$ docker system prune -a -f
+docker system prune -a -f
 ```
 
 ## Version incompatibilities

doc/contributor/native-image.md

@@ -58,18 +58,18 @@ startup performance than MRI.
 Run on Linux with an Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz with a SSD.
 
 ```bash
-$ cd graalvm-ce-1.0.0-rc15
-$ bin/ruby -e 'puts "Hello"'       # TruffleRuby on the SVM
-$ bin/ruby --jvm -e 'puts "Hello"' # TruffleRuby on the JVM
+cd graalvm-ce-1.0.0-rc15
+bin/ruby -e 'puts "Hello"'       # TruffleRuby on the SVM
+bin/ruby --jvm -e 'puts "Hello"' # TruffleRuby on the JVM
 
-$ chruby ruby-2.6.2
-$ ruby -e 'puts "Hello"'
+chruby ruby-2.6.2
+ruby -e 'puts "Hello"'
 
-$ chruby rbx-3.107
-$ rbx -e 'puts "Hello"'
+chruby rbx-3.107
+rbx -e 'puts "Hello"'
 
-$ chruby jruby-9.2.7.0
-$ jruby -e 'puts "Hello"'
+chruby jruby-9.2.7.0
+jruby -e 'puts "Hello"'
 ```
 
 The real time and the maximum resident set size are measured with a custom
@@ -84,7 +84,7 @@ the Native Image version of TruffleRuby using a tool distributed as part of Graa
 the Java version of TruffleRuby from GraalVM.
 
 ```bash
-$ native-image -H:Name=native-ruby --language:ruby
+native-image -H:Name=native-ruby --language:ruby
 ```
 
 `native-ruby` is the output file name.
@@ -93,7 +93,7 @@ You can build a native build of TruffleRuby using the Native Image Tool from a
 source distribution using:
 
 ```bash
-$ jt build --env native
+jt build --env native
 ```
 
 The disadvantages of the Native Image version of TruffleRuby are:

doc/contributor/profiling.md

@@ -27,13 +27,13 @@ handled by the `open` command on macOS and the `xdg-open` command on Linux.
 To illustrate, here's a command for profiling and inline script.
 
 ```bash
-$ jt profile -e "x = 'abc'; 100_000.times { x.upcase }"
+jt profile -e "x = 'abc'; 100_000.times { x.upcase }"
 ```
 
 Here's a command for profiling the `gem list` command:
 
 ```bash
-$ jt profile -S gem list
+jt profile -S gem list
 ```
 
 #### The Less Easy Way
@@ -48,7 +48,7 @@ Creating the flame graph is a multi-stage process. First, we need to profile the
 with the JSON formatter:
 
 ```bash
-$ jt ruby --cpusampler --cpusampler.SampleInternal --cpusampler.Mode=roots --cpusampler.Output=json -e 'p :hello' > simple-app.json
+jt ruby --cpusampler --cpusampler.SampleInternal --cpusampler.Mode=roots --cpusampler.Output=json -e 'p :hello' > simple-app.json
 ```
 
 Since we want to profile the TruffleRuby runtime itself, we use the
@@ -67,7 +67,7 @@ into TruffleRuby's parent directory. Now you can run the script to transform the
 pipe it into the script that will generate the SVG data:
 
 ```bash
-$ ../FlameGraph/stackcollapse-graalvm.rb simple-app.json | ../FlameGraph/flamegraph.pl > simple-app.svg
+../FlameGraph/stackcollapse-graalvm.rb simple-app.json | ../FlameGraph/flamegraph.pl > simple-app.svg
 ```
 
 At this point, you should open the SVG file in a Chromium-based web browser. Your system

doc/contributor/static-analysis.md

@@ -12,8 +12,8 @@ code. We occasionally run this tool locally but only take its output as a
 suggestion. We use a default configuration.
 
 ```bash
-$ scan-build --use-analyzer `which clang` -analyze-headers clang -c --std=c99 -Ilib/cext/include src/main/c/cext/ruby.c src/main/c/truffleposix/truffleposix.c
-$ scan-view ...as instructed by scan-build...
+scan-build --use-analyzer `which clang` -analyze-headers clang -c --std=c99 -Ilib/cext/include src/main/c/cext/ruby.c src/main/c/truffleposix/truffleposix.c
+scan-view ...as instructed by scan-build...
 ```
 
 ## Java
@@ -24,7 +24,7 @@ We have a tool to check that some use of our internal annotations and the
 Truffle DSL are correct. Passing this is enforced in our CI gate.
 
 ```bash
-$ jt check_dsl_usage
+jt check_dsl_usage
 ```
 
 ### CheckStyle
@@ -33,7 +33,7 @@ $ jt check_dsl_usage
 Passing CheckStyle is enforced in our CI gate.
 
 ```bash
-$ mx checkstyle
+mx checkstyle
 ```
 
 ### SpotBugs
@@ -43,7 +43,7 @@ errors. We run it with the default Graal project configuration. Passing
 SpotBugs is enforced in our CI gate.
 
 ```bash
-$ mx spotbugs
+mx spotbugs
 ```
 
 ## Ruby
@@ -55,7 +55,7 @@ It's configured in `.rubocop.yml`, and can be run locally as `jt rubocop`.
 Passing Rubocop is enforced in our CI gate.
 
 ```bash
-$ jt rubocop
+jt rubocop
 ```
 
 ### Fasterer
@@ -65,8 +65,8 @@ performance improvements. We occasionally run this tool locally but only take
 its output as a suggestion. We use a default configuration.
 
 ```bash
-$ gem install fasterer
-$ fasterer lib/truffle lib/cext src/main
+gem install fasterer
+fasterer lib/truffle lib/cext src/main
 ```
 
 ### Reek
@@ -79,8 +79,8 @@ we're implementing a set API, because we're doing something low-level or
 outside normal Ruby semantics, or for performance reasons.
 
 ```bash
-$ gem install reek
-$ reek lib/truffle lib/cext src/main
+gem install reek
+reek lib/truffle lib/cext src/main
 ```
 
 ### Flog
@@ -90,8 +90,8 @@ check that your methods do not appear near the top of this list. We
 occasionally run this tool locally but only take its output as a suggestion.
 
 ```bash
-$ gem install flog
-$ flog -m -t 10 lib/truffle lib/cext src/main
+gem install flog
+flog -m -t 10 lib/truffle lib/cext src/main
 ```
 
 ### Flay
@@ -101,8 +101,8 @@ could potentially be factored out. We occasionally run this tool locally but
 only take its output as a suggestion.
 
 ```bash
-$ gem install flay
-$ flay lib/truffle lib/cext src/main
+gem install flay
+flay lib/truffle lib/cext src/main
 ```
 
 ### Brakeman
@@ -113,6 +113,6 @@ specific to Rails, but we do run it ocassionally anyway and take its output as
 a suggestion.
 
 ```bash
-$ gem install brakeman
-$ brakeman --force-scan --run-all-checks --interprocedural --no-pager --add-libs-path src --only-files lib/truffle/,lib/cext/,src/main/ruby/truffleruby/
+gem install brakeman
+brakeman --force-scan --run-all-checks --interprocedural --no-pager --add-libs-path src --only-files lib/truffle/,lib/cext/,src/main/ruby/truffleruby/
 ```

doc/contributor/stdlib.md

@@ -124,14 +124,14 @@ TruffleRuby in the future, as some default gems we use differ from the originals
 
 To list default gems, use:
 ```
-$ gem list | grep default:
+gem list | grep default:
 ```
 
 ### Bundled gems
 
 The list of bundled gems is available in MRI under `gems/bundled_gems`
 ```
-$ cat gems/bundled_gems
+cat gems/bundled_gems
 ```
 
 * `did_you_mean` 1.3.0 (helper to suggest method names on method missing)

doc/contributor/updating-jruby-parser.md

@@ -8,7 +8,7 @@ First, checkout JRuby in `../jruby`.
 TruffleRuby's version of the parser:
 
 ```bash
-$ ruby tool/parser_renames.rb < ../jruby/core/src/main/java/org/jruby/parser/RubyParser.y > src/main/java/org/truffleruby/parser/parser/RubyParser.y
+ruby tool/parser_renames.rb < ../jruby/core/src/main/java/org/jruby/parser/RubyParser.y > src/main/java/org/truffleruby/parser/parser/RubyParser.y
 ```
 
 Use it like `tool/import-mri-files.sh` is used in [Updating Ruby](updating-ruby.md).

doc/contributor/updating-ruby-installers.md

@@ -28,7 +28,7 @@ maintained in the [ruby-versions](https://github.com/postmodern/ruby-versions) r
 There is a handy script in the repo that does everything needed:
 
 ```bash
-$ ./update.sh truffleruby $VERSION
+./update.sh truffleruby $VERSION
 ```
 
 cc `@havenwood` in the PR description.
@@ -38,7 +38,7 @@ cc `@havenwood` in the PR description.
 There is a script in the repo that does everything needed:
 
 ```bash
-$ script/update-truffleruby $VERSION ../ruby-versions/pkg
+script/update-truffleruby $VERSION ../ruby-versions/pkg
 ```
 
 cc `@hsbt` in the PR description.
@@ -52,7 +52,7 @@ Once pushed/merged to master, it's a good idea to create a `ruby-build` release,
 so `ruby-build` Homebrew users can get the new TruffleRuby release too:
 
 ```bash
-$ script/release
+script/release
 ```
 
 See [this comment](https://github.com/rbenv/ruby-build/pull/1318#issuecomment-548399571) for details.
@@ -62,7 +62,7 @@ See [this comment](https://github.com/rbenv/ruby-build/pull/1318#issuecomment-54
 There is a script in the repo that does everything needed:
 
 ```bash
-$ ruby update-truffleruby.rb $VERSION ../ruby-versions/pkg
+ruby update-truffleruby.rb $VERSION ../ruby-versions/pkg
 ```
 
 The script must be run after running the `ruby-versions` script above.

doc/contributor/updating-ruby.md

@@ -18,9 +18,9 @@ Check out the version of Ruby you want to create the branch for in `../ruby`.
 Then create the reference branch in the TruffleRuby repository
 
 ```bash
-$ git checkout -b vNN
-$ tool/import-mri-files.sh
-$ git commit -am 'vNN'
+git checkout -b vNN
+tool/import-mri-files.sh
+git commit -am 'vNN'
 ```
 
 You can then compare between these two branches and yours. For example to see
@@ -36,8 +36,8 @@ In your working branch you can import MRI files again, and you can re-apply
 old patches using the old reference branch.
 
 ```bash
-$ tool/import-mri-files.sh
-$ git revert vNN
+tool/import-mri-files.sh
+git revert vNN
 ```
 
 You'll usually get some conflicts to work out.

doc/contributor/using-eclipse.md

@@ -16,13 +16,13 @@ need a full rebuild. For these reason, we recommend
 First, make sure the project is already built from the command line:
 
 ```bash
-$ jt build
+jt build
 ```
 
 ## Generate the Project Files
 
 ```bash
-$ jt mx eclipseinit
+jt mx eclipseinit
 ```
 
 ## Import the Projects
@@ -44,6 +44,6 @@ There should be now 4 projects in your workspace:
 ## Running from the Eclipse Files Directly
 
 ```bash
-$ jt ruby -e 'p Truffle'
+jt ruby -e 'p Truffle'
 Truffle
 ```