mirror of
				https://github.com/cheat/cheat.git
				synced 2025-11-04 07:45:28 +01:00 
			
		
		
		
	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:
		@@ -8,11 +8,11 @@ colorize: false
 | 
			
		||||
# Which 'chroma' colorscheme should be applied to the output?
 | 
			
		||||
# Options are available here:
 | 
			
		||||
#   https://github.com/alecthomas/chroma/tree/master/styles
 | 
			
		||||
# style: monokai
 | 
			
		||||
style: monokai
 | 
			
		||||
 | 
			
		||||
# Which 'chroma' "formatter" should be applied?
 | 
			
		||||
# One of: "terminal", "terminal256", "terminal16m"
 | 
			
		||||
formatter: terminal
 | 
			
		||||
formatter: terminal256
 | 
			
		||||
 | 
			
		||||
# Through which pager should output be piped?
 | 
			
		||||
# '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
 | 
			
		||||
# 'community' rather than your own, you can use: cheat tar -t community
 | 
			
		||||
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.
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user