From f1cdfa6dd977c729b0b0611d242ebaa506124ba7 Mon Sep 17 00:00:00 2001 From: Chris Lane Date: Sat, 14 Sep 2013 11:35:16 -0400 Subject: [PATCH] Updated the README. --- README.md | 21 ++++++--------------- 1 file changed, 6 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 1457dd4..28d7a9c 100644 --- a/README.md +++ b/README.md @@ -128,25 +128,16 @@ Creating/Editing Cheatsheets Provided that you have an `EDITOR` environment variable set, you may create new cheatsheets via: -```bash -cheat -c foo -``` - -By default, `cheat` will attempt to write the new cheatsheet to `~/.cheat`, -creating the `~/.cheat` directory if necessary. (If it is unable to do so, the -new cheatsheet will be written to the default cheatsheet directory instead, -though this will likely require `sudo`.) - -Likewise, an existing cheatsheet may be edited via: - ```bash cheat -e foo ``` -Command Autocompletion in zsh ------------------------------ -`zsh` users may use `cheat -d` in coordination with the provided `\_cheat` file -to implement autocompletion [as described here][4]. +If the 'foo' cheatsheet already exists, it will be opened for editing. + +By default, `cheat` will attempt to write new cheatsheets to `~/.cheat`, and +will create the `~/.cheat` directory if necessary. If it is unable to do so, +the new cheatsheet will be written to the default cheatsheet directory instead, +though this will likely require `sudo`. Contributing