diff options
| author | Mark Wagie | 2020-03-10 17:50:37 -0600 |
|---|---|---|
| committer | Joost Bremmer | 2020-04-10 01:36:33 +0200 |
| commit | ccb5c4a7755deaea85c14e680898bf266fad8900 (patch) | |
| tree | 453100485294f6248d35d18c09a3c668e046a670 /conf.yml | |
| parent | c9a454f6ace8af00760f3b4b1c6112543c433c27 (diff) | |
| download | aur-ccb5c4a7755deaea85c14e680898bf266fad8900.tar.gz | |
upgpkg: cheat 3.7.0-2
update conf.yml from upstream
Diffstat (limited to 'conf.yml')
| -rw-r--r-- | conf.yml | 25 |
1 files changed, 13 insertions, 12 deletions
@@ -32,11 +32,12 @@ cheatpaths: # thus be overridden by more local cheatsheets. That being the case, you # should probably list community cheatsheets first. # - # Note that the paths and tags listed below are just examples. You may freely + # Note that the paths and tags listed below are placeholders. You may freely # change them to suit your needs. # - # TODO: regarding community cheatsheets: these must be installed separately. - # You may download them here: + # Community cheatsheets must be installed separately, though you may have + # downloaded them automatically when installing 'cheat'. If not, you may + # download them here: # # https://github.com/cheat/cheatsheets # @@ -49,16 +50,16 @@ cheatpaths: # If you have personalized cheatsheets, list them last. They will take # precedence over the more global cheatsheets. - #- name: personal - # path: ~/cheat/cheatsheets/personal - # tags: [ personal ] - # readonly: false + - name: personal + path: PERSONAL_PATH + 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. + # While it requires no 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, |