-
Notifications
You must be signed in to change notification settings - Fork 39
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #942 from Mic92/joerg-ci
flake.lock: Update
- Loading branch information
Showing
22 changed files
with
250 additions
and
127 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,47 +1,82 @@ | ||
--- | ||
# The editor to use with 'cheat -e <sheet>'. Defaults to $EDITOR or $VISUAL. | ||
#editor: vim | ||
# 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: dracula | ||
style: solarized-light | ||
|
||
# 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. | ||
# Through which pager should output be piped? | ||
# 'less -FRX' is recommended on Unix systems | ||
# 'more' is recommended on Windows | ||
pager: less -FRX | ||
|
||
# Cheatpaths are paths at which cheatsheets are available on your local | ||
# filesystem. | ||
# | ||
# It is useful to sort cheatsheets into different cheatpaths for organizational | ||
# purposes. For example, you might want one cheatpath for community | ||
# cheatsheets, one for personal cheatsheets, one for cheatsheets pertaining to | ||
# your day job, one for code snippets, etc. | ||
# | ||
# Cheatpaths are scoped, such that more "local" cheatpaths take priority over | ||
# more "global" cheatpaths. (The most global cheatpath is listed first in this | ||
# file; the most local is listed last.) For example, if there is a 'tar' | ||
# cheatsheet on both global and local paths, you'll be presented with the local | ||
# one by default. ('cheat -p' can be used to view cheatsheets from alternative | ||
# cheatpaths.) | ||
# | ||
# Cheatpaths can also be tagged as "read only". This instructs cheat not to | ||
# automatically create cheatsheets on a read-only cheatpath. Instead, when you | ||
# would like to edit a read-only cheatsheet using 'cheat -e', cheat will | ||
# perform a copy-on-write of that cheatsheet from a read-only cheatpath to a | ||
# writeable cheatpath. | ||
# | ||
# This is very useful when you would like to maintain, for example, a | ||
# "pristine" repository of community cheatsheets on one cheatpath, and an | ||
# editable personal reponsity of cheatsheets on another cheatpath. | ||
# | ||
# 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. | ||
# Cheatpaths can be also configured to automatically apply tags to cheatsheets | ||
# on certain paths, which can be useful for querying purposes. | ||
# Example: 'cheat -t work jenkins'. | ||
# | ||
# But what if you want to view the "upstream" cheatsheets instead of your own? | ||
# Cheatsheets may be filtered via 'cheat -f <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 -f community | ||
# 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 | ||
cheatpaths: | ||
|
||
# Paths that come earlier are considered to be the most "global", and will | ||
# 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 | ||
# change them to suit your needs. | ||
# Cheatpath properties mean the following: | ||
# 'name': the name of the cheatpath (view with 'cheat -d', filter with 'cheat -p') | ||
# 'path': the filesystem path of the cheatsheet directory (view with 'cheat -d') | ||
# 'tags': tags that should be automatically applied to sheets on this path | ||
# 'readonly': shall user-created ('cheat -e') cheatsheets be saved here? | ||
- name: community | ||
path: ~/git/cheatsheets | ||
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: x86 | ||
path: ~/git/x86_64-linux-cheatsheats/pages/ | ||
tags: [ x86 ] | ||
# If you have personalized cheatsheets, list them last. They will take | ||
# precedence over the more global cheatsheets. | ||
- name: personal | ||
path: ~/git/x86_64-linux-cheatsheats/pages | ||
tags: [ personal ] | ||
readonly: false | ||
|
||
# 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. Similarly, | ||
# directory-scoped cheatsheets will always be editable ('readonly: false'). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.