Chris Allen Lane

For what it's worth, @chubin, the front-matter approach has been working well for `cheat` so far. In my opinion, it has two primary advantages: 1. This pattern is well-understood by...

Hi, @chubin Sorry for the delay once again. Things have been hectic. Currently, `cheat` only supports two properties in front-matter: - `syntax` (string): the syntax highlighter to use on output...

+1 for linting cheatsheets. I've been considering doing the same in `cheat/cheatsheets` as well. I've been considering linting along the following lines: 1. Comment lines should begin with `# To`...

I've added a few tags to this ticket to help community contributors to find it :slightly_smiling_face:

Hi, @bannmann Thanks for your work on `docker-cheat`! Regarding the README situation - yeah, I'm aware that it doesn't link to the wiki currently, and I agree that's not ideal....

Hi, @smbambling Thanks for the feature request. > This might be able to be easily achieved by not copying an existing community file on edit and then outputting all files...

Thanks for reporting this, @EmilySeville7cfg. There was indeed important information missing here. I've improved the configuration documentation in the `4.3.2` release: https://github.com/cheat/cheat/releases/tag/4.3.2 I'm thus going to close this as resolved.

I'm sorry, but I'm going to have to ask some dumb questions here, because I haven't kept up with the Go ecosystem as closely as I should have: 1. What...

Hi, @zeitchef. Thanks for the thoughtful and thorough feature-request. Regarding the `cheat -l` output: I agree it's a bit gross right now. Having used `cheat@v3` for a little while now,...

Yeah, shell completion is one of my higher priorities now, and for the shells you've listed. I need to read up on how to implement this properly, but I agree...