path: root/dotfiles/config/cheat/conf.yml
diff options
authorcbreton <c.breton@fullsave.com>2020-01-09 10:42:26 +0100
committercbreton <c.breton@fullsave.com>2020-01-09 10:42:26 +0100
commitf86d315c79f1ea2cfec263f412931a6a33db5179 (patch)
tree33f844ab12f616e19e0f09965f25860ff5cba84a /dotfiles/config/cheat/conf.yml
parentecc25dcecac342a7b39376ba969f1c5ea25a8aaa (diff)
Update cheat to the last version
Diffstat (limited to '')
1 files changed, 39 insertions, 0 deletions
diff --git a/dotfiles/config/cheat/conf.yml b/dotfiles/config/cheat/conf.yml
new file mode 100644
index 0000000..f249549
--- /dev/null
+++ b/dotfiles/config/cheat/conf.yml
@@ -0,0 +1,39 @@
+# The editor to use with 'cheat -e <sheet>'. Defaults to $EDITOR or $VISUAL.
+#editor: vim
+# Should 'cheat' always colorize output?
+colorize: true
+# Which 'chroma' colorscheme should be applied to the output?
+# Options are available here:
+# https://github.com/alecthomas/chroma/tree/master/styles
+style: monokai
+# Which 'chroma' "formatter" should be applied?
+# One of: "terminal", "terminal256", "terminal16m"
+formatter: terminal16m
+# The paths at which cheatsheets are available. Tags associated with a cheatpath
+# are automatically attached to all cheatsheets residing on that path.
+# Whenever cheatsheets share the same title (like 'tar'), the most local
+# cheatsheets (those which come later in this file) take precedent over the
+# less local sheets. This allows you to create your own "overides" for
+# "upstream" cheatsheets.
+# But what if you want to view the "upstream" cheatsheets instead of your own?
+# Cheatsheets may be filtered via 'cheat -t <tag>' in combination with other
+# commands. So, if you want to view the 'tar' cheatsheet that is tagged as
+# 'community' rather than your own, you can use: cheat tar -t community
+ - name: work
+ path: ~/.bcheat
+ tags: [ work ]
+ readonly: false
+ - name: personal
+ path: ~/.cheat
+ tags: [ personal ]
+ readonly: false