aboutsummaryrefslogtreecommitdiff
path: root/README.markdown
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2013-09-09 20:03:06 +1200
committerTom Ryder <tom@sanctum.geek.nz>2013-09-09 20:03:06 +1200
commitff36421d87e80eca667df2232674338e475f70a7 (patch)
tree5f2d36d4453f4252899ed2988fafd663e3f21cd7 /README.markdown
parentHardcode install script name in error output (diff)
downloaddotfiles-ff36421d87e80eca667df2232674338e475f70a7.tar.gz
dotfiles-ff36421d87e80eca667df2232674338e475f70a7.zip
Use fenced code blocks
Diffstat (limited to 'README.markdown')
-rw-r--r--README.markdown8
1 files changed, 6 insertions, 2 deletions
diff --git a/README.markdown b/README.markdown
index 686bdd2d..a7e7aea6 100644
--- a/README.markdown
+++ b/README.markdown
@@ -79,12 +79,16 @@ work with [any version 2.05a or newer][18]. This is the version in which the
less error-prone `[[` test syntax was introduced. This is why I use older
syntax for certain things such as appending items to arrays:
- array[${#array[@]}]=$item
+```bash
+array[${#array[@]}]=$item
+```
Compare this to the much nicer syntax available since 3.1-alpha1, which
actually works for arrays with sparse indexes, unlike the above syntax:
- array+=("$item")
+```bash
+array+=("$item")
+```
My prompt generally looks like this, colored bright green: