There should be way more examples for bash string usage:

${foo:2}
${foo%…}
${foo#…}
${foo##…}

etc.

@carlogarro wrote:

It could be nice to have a guide for automounting devices. And for that, [fstab](https://en.wikipedia.org/wiki/Fstab) is necessary.
Just giving some ideas.

Amazing work, by the way!

(from chubin/cheat.sh#281)

For example, cowsay is on the site but not in the gh repo.

What about adding i3 cheatsheet? I can write it and send pull request if you want to.

Create a new cheat sheet, for the jq command.

Besides the main purpose of the cheat sheet, coverage of the jq command,
it could be a test bed for such fearures:

• Big sectioned cheat sheet
• support for example output for commands.

There could be something for Spring Boot CLI, so cheat.sh/spring, I think I could take a look into it 😼🔎

I'm not sure why but the formatting of curl cht.sh/awk seems to return the json payload

> curl https://cht.sh/awk
{"topic": "awk", "answer": "# sum integers from a file or stdin, one integer per line:\nprintf '1\\n2\\n3\\n' | awk '{ sum += $1} END {print sum}'\n\n# using specific character as separator to sum integers from a file or stdin\nprintf '1:2:3' | awk -F \":\" '{print $1+$2+$3}'\n\n# print a multiplication table\nseq 9 | sed 'H;g' | awk -v RS='' '{for(i=1;i<=NF;i++)printf(\"%dx%d=%d%s\", i, NR, i*NR, i==NR?\"\\n\":\"\\t\")}'\n\n# Specify output separator character\nprintf '1 2 3' | awk 'BEGIN {OFS=\":\"}; {print $1,$2,$3}'\n\n# search for a paragraph containing string\nawk -v RS='' '/42B/' file\n", "topic_type": "cheat.sheets", "format": "code"}

When I would expect a more readable format like so:

> curl https://cht.sh/ls
# Displays everything in the target directory
ls path/to/the/target/directory

# Displays everything including hidden files
ls -a

# Displays all files, along with the size (with unit suffixes) and timestamp
ls -lh 

# Display files, sorted by size
ls -S

# Display directories only
ls -d */

# Display directories only, include hidden
ls -d .*/ */

Do people really need a section about telnet in the cheatsheet?

Or, maybe, we could just split them into different files:

• emacs/telnet
• emacs/dired

I feel like the main page should be as short as possible and contain only essential info and refer other pages.

Hi @chubin !

I don't recall seeing a method by which I or another can contact you -- might be nice to set up an E-Mail for that, for these awesome projects of yours, if you haven't already done so. It would save creating issues like this.

Okay, so my question, regarding the formatting of the sheets, is whether this is preferred:

# CMD
# Short description

...

Or this, apt-cache(1) search style:

# CMD - Short description

...

Or this:

# CMD
#
# Short description

...

Reason being, my OCD screams at me when I see inconsistencies (lol), and I was hoping to, if you'd like, go through each of the cheets to make it either one of those styles, or perhaps another of your choosing.

What think you?

Todo

• all cheat sheets from all upstream repositories must be shown by default
• there are must be a way do address a cheat sheet from some repository directly (say: cheat:cpdf).

Details

Previously, I would just add cheat sheets to https://github.com/cheat/cheatsheets

But now, I'm a bit confused.

Say, I want to add a new jq sheet. There's one in this repo: https://github.com/chubin/cheat.sheets/blob/master/sheets/jq and this is the one that is served when querying cht.sh jq

Then there's this one https://github.com/cheat/cheatsheets/blob/master/jq

Which of the two should I update so that most people benefit from the change?

If the answer is both, can something be done about this?

/cc @chrisallenlane

By having filenames like :main git will fail to clone the repository on windows with error
error: unable to create file sheets/_scala/:main: Invalid argument