Skip to content

Alternative output format for cheat -l #505

@zeitchef

Description

@zeitchef

Is your feature request related to a problem? Please describe.
I prefer to keep my shell/text editor rather narrow and to the side. The problem is when listing all my available cheatsheets, the shell output is rather cramped and hard to read. In addition, I've created sub-folders inside my personal directory to scope cheatsheets further, it would be much more readable to be able to list cheatsheets by scope.

Describe the solution you'd like
I'd like to propose an alternative format for the cheat -l command.

css
  bem               css, webdevelopment
  selectors         css, webdevelopment
  transition        animation, css, webdevelopment

js
  array             array, datasctructure, javascript
  fetch             api, http, javascript, webdevelopment

This way, output is much more readable and friendlier to the narrower shell users.

Describe alternatives you've considered
An alternative to this approach would be to remove the file: output from cheat -l. It's rare that I'm interested in the exact filepath of the cheatsheet (since I've scoped them, I know basically where they are). In the case that I would like to find the filepath, a cheat <cheatsheet> --info command could be useful.

Additional context
This is my current output:
Screen Shot 2019-11-15 at 12 35 04

Rails 6 recently added something similar for its rails routes command. This was notoriously messy output. The addition of an --expanded flag outputs much more streamlined.

Rails 6 shows routes in expanded format - BigBinary

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions