Git
/
cheat
mirror of https://github.com/cheat/cheat.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix: no colorization on default install (#687) 

Fix an issue whereby a default installation (as created by the
installer) would (seemingly) fail to output colorized text, even when
the `-c` flag was passed.

The root cause of the problem was that the installer did not set a
default `style` for `chroma`, which in turn defaulted to using the `bw`
(black-and-white) style.

Thus, colorization actually *was* being applied with `-c` - it was
simply black and white!
This commit is contained in:
Christopher Allen Lane 2022-08-08 19:45:32 -04:00
parent 77f9c3fdd0
commit 0c47f44ff9
2 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
cmd/cheat/str_config.go
View File

@ -17,11 +17,11 @@ colorize: false
# Which 'chroma' colorscheme should be applied to the output? # Which 'chroma' colorscheme should be applied to the output?
# Options are available here: # Options are available here:
# https://github.com/alecthomas/chroma/tree/master/styles # https://github.com/alecthomas/chroma/tree/master/styles
# style: monokai style: monokai
# Which 'chroma' "formatter" should be applied? # Which 'chroma' "formatter" should be applied?
# One of: "terminal", "terminal256", "terminal16m" # One of: "terminal", "terminal256", "terminal16m"
formatter: terminal formatter: terminal256
# Through which pager should output be piped? # Through which pager should output be piped?
# 'less -FRX' is recommended on Unix systems # 'less -FRX' is recommended on Unix systems
@ -41,7 +41,6 @@ pager: PAGER_PATH
# commands. So, if you want to view the 'tar' cheatsheet that is tagged as # 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 # 'community' rather than your own, you can use: cheat tar -t community
cheatpaths: cheatpaths:
# Paths that come earlier are considered to be the most "global", and will # 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 # thus be overridden by more local cheatsheets. That being the case, you
# should probably list community cheatsheets first. # should probably list community cheatsheets first.

5
configs/conf.yml
View File

@ -8,11 +8,11 @@ colorize: false
# Which 'chroma' colorscheme should be applied to the output? # Which 'chroma' colorscheme should be applied to the output?
# Options are available here: # Options are available here:
# https://github.com/alecthomas/chroma/tree/master/styles # https://github.com/alecthomas/chroma/tree/master/styles
# style: monokai style: monokai
# Which 'chroma' "formatter" should be applied? # Which 'chroma' "formatter" should be applied?
# One of: "terminal", "terminal256", "terminal16m" # One of: "terminal", "terminal256", "terminal16m"
formatter: terminal formatter: terminal256
# Through which pager should output be piped? # Through which pager should output be piped?
# 'less -FRX' is recommended on Unix systems # 'less -FRX' is recommended on Unix systems
@ -32,7 +32,6 @@ pager: PAGER_PATH
# commands. So, if you want to view the 'tar' cheatsheet that is tagged as # 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 # 'community' rather than your own, you can use: cheat tar -t community
cheatpaths: cheatpaths:
# Paths that come earlier are considered to be the most "global", and will # 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 # thus be overridden by more local cheatsheets. That being the case, you
# should probably list community cheatsheets first. # should probably list community cheatsheets first.