updated to 3.4.1

1 files changed, 14 insertions, 11 deletions

diff --git a/conf.yml b/conf.yml
index d4402bc867fb..d214f5f79bc5 100644
--- a/conf.yml
+++ b/conf.yml
@@ -1,6 +1,6 @@
 ---
 # The editor to use with 'cheat -e <sheet>'. Defaults to $EDITOR or $VISUAL.
-#editor: vim
+editor: vim
 
 # Should 'cheat' always colorize output?
 colorize: true
@@ -47,16 +47,19 @@ cheatpaths:
     tags: [ community ]
     readonly: true
 
-  # Maybe your company or department maintains a repository of cheatsheets as
-  # well. It's probably sensible to list those second.
-  #- name: work
-    #path: ~/.dotfiles/cheat/work
-    #tags: [ work ]
-    #readonly: false
-
   # If you have personalized cheatsheets, list them last. They will take
   # precedence over the more global cheatsheets.
   #- name: personal
-    #path: ~/.dotfiles/cheat/personal
-    #tags: [ personal ]
-    #readonly: false
+  #  path: ~/cheat/cheatsheets/personal
+  #  tags: [ personal ]
+  #  readonly: false
+
+  # While it requires no specific configuration here, it's also worth noting
+  # that 'cheat' will automatically append directories named '.cheat' within
+  # the current working directory to the 'cheatpath'. This can be very useful
+  # if you'd like to closely associate cheatsheets with, for example, a
+  # directory containing source code.
+  #
+  # Such "directory-scoped" cheatsheets will be treated as the most "local"
+  # cheatsheets, and will override less "local" cheatsheets. Likewise,
+  # directory-scoped cheatsheets will always be editable ('readonly: false').