diff options
author | zlg <zlg@zlg.space> | 2018-10-18 21:06:58 -0700 |
---|---|---|
committer | zlg <zlg@zlg.space> | 2018-10-18 21:06:58 -0700 |
commit | deb34f6cb8902277ac4cf4feca1b44c1ba085f98 (patch) | |
tree | 11913b90fa8cadd5f3a1b1cdf8f3d7bd45c44cc0 | |
parent | cli: show msg if game to be deleted is not in DB (diff) | |
download | vgstash-deb34f6cb8902277ac4cf4feca1b44c1ba085f98.tar.gz vgstash-deb34f6cb8902277ac4cf4feca1b44c1ba085f98.tar.bz2 vgstash-deb34f6cb8902277ac4cf4feca1b44c1ba085f98.tar.xz vgstash-deb34f6cb8902277ac4cf4feca1b44c1ba085f98.zip |
README: fix inline <code> formatting
-rw-r--r-- | README.md | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -104,8 +104,9 @@ $ vgstash add 'Mario Kart: Double Dash!!' GCN p n ``` Note that we're using single quotes; if we used double quotes, then the `!!` -would expand to the last command entered into the shell, creating `Mario Kart: -Double Dash<your last command here>`. Quite different from what you'd expect! +would expand to the last command entered into the shell, creating +`Mario Kart: Double Dash<your last command here>`. Quite different from what +you'd expect! But what if we, somehow, had both single quotes *and* sequential exclamation points? Single-quoted strings cannot escape a single quote character. Double @@ -133,7 +134,7 @@ quotes; then an escaped single quote for literal output; then `s crazy!!` in single quotes to avoid the `!!` expansion. The last option is to disable the feature (history expansion) altogether, though -you'll miss out on nice stuff like `sudo !!`. In bash, it's disabled with `set +you'll miss out on nice stuff like `sudo !!`. In bash, it's disabled with `set +H` or `set +o histexpand`. Change `+` to `-` to turn it back on when you're done. |