Weirdly, I’ve never thought of keeping a single cheatsheet for command line snippets.
I’ll usually put relevant commands into my project README files but your post has inspired me to start a global cheatsheet of common commands too!
Ask HN: Can I see your cheatsheet?
151–160 of 173 posts
Re: Ask HN: Can I see your cheatsheet?
#152http://cht.sh/ - I use this a lot. It outputs a short summary of common commands for many cli tools. You can curl to it https://cht.sh/grep for example or install their cli client
This is awesome! Thank you! I am so frequently visiting https://tmuxcheatsheet.com/, and it's not even that great of a cheat sheet.
Re: Ask HN: Can I see your cheatsheet?
#153One of the most useful cheat sheet utilities I've come across is cheat.sh: https://github.com/chubin/cheat.sh If you don't have it installed it can easily be queried with curl from the command line like: `curl cheat.sh/sed`. The payload is colorized and gives a lot of examples of usage of the command. You can also query "cht.sh" to use fewer characters. There is actually a lot more advanced usage of the tool/service…
Wow. All I can say is thank you. This is great.
Re: Ask HN: Can I see your cheatsheet?
#154I keep my "lab" diary in txt files for each day and use VSCode.
Would not ever post any of it because these are mostly specific command lines.
Then with VSCode if I need to remind myself of something I search for command I might use and get my whole history with contexts. Then I copy paste/change and keep all that history there.
Never ever I will spend time organizing it into cheat-sheet because it will be waste of time anything that I put into cheat-sheet that I won't use in next 6-12 months will be just cluttering space on such cheat-sheet.
Re: Ask HN: Can I see your cheatsheet?
#155Earlier quoted context omitted.
This. I've been doing this for a couple of years now, I'm really used to it. I've been "traveling" with my history that is over 70k lines. My dot alias file has only 3 aliases (c=clear, q=exit, gti=git). Hope there's a project out there that helps parse, rank, or do something with a file like this. There must be interesting information.
Is gti=git for capturing typos or some other reason?
It's a typo, but I make it a lot!
Re: Ask HN: Can I see your cheatsheet?
#156I use my ebooks for reference: * GNU grep and ripgrep ( https://learnbyexample.github.io/learn_gnugrep_ripgrep/ ) * GNU sed ( https://learnbyexample.github.io/learn_gnused/ ) * GNU awk ( https://learnbyexample.github.io/learn_gnuawk/ ) * Ruby one-liners cookbook ( https://learnbyexample.github.io/learn_ruby_oneliners/ ) * Perl one-liners cookbook ( https://learnbyexample.github.io/learn_perl_oneliners/ ) * Command li…
Great work! Seriously cool e-books!
(edit: reading this i sound like a jerk. wasn’t trying to be one.) However, these are books not cheat sheets. Cheat sheets are about glance ability and one page ness.
Re: Ask HN: Can I see your cheatsheet?
#157I use my ebooks for reference: * GNU grep and ripgrep ( https://learnbyexample.github.io/learn_gnugrep_ripgrep/ ) * GNU sed ( https://learnbyexample.github.io/learn_gnused/ ) * GNU awk ( https://learnbyexample.github.io/learn_gnuawk/ ) * Ruby one-liners cookbook ( https://learnbyexample.github.io/learn_ruby_oneliners/ ) * Perl one-liners cookbook ( https://learnbyexample.github.io/learn_perl_oneliners/ ) * Command li…
I consider myself pretty experienced at shell-fu and capable of doing most things I set out to achieve in either bash scripts or fearless one-liners. However, my awk is rudimentary at best, I think mostly because it's such an unforgiving environment to experiment in. These books you've written are great for a bit of first principles insight and then quickly building up to functional usage. I will have no hesitation i…
I suggest:
C-x C-e in the CLI (not sure if it’s zsh only) will open your command line in your $EDITOR - useful to get code highlighting and write multi line commands if that’s the blocker. The problem is iterating.
OR
Pipe your awk input to a file and then use this thing I wrote to build up your awk program. I use it most often with `jq`.
Re: Ask HN: Can I see your cheatsheet?
#158Set a huuuuuuuge shell history https://github.com/craigjperry2/dotfiles/blob/aa77ddcbde63bf... then fzf ctrl+r bindings mean you can recall anything right where you need it. If you’re going to do this then have an escape hatch for commands you don’t want memorised https://github.com/craigjperry2/dotfiles/blob/aa77ddcbde63bf...
I‘ve been doing this ever since I migrated from Windows to Mac in 2015. My bash history has over 40k lines, datestamped. I can recall any command I have typed in my terminal in the past seven years. Extremely helpful whenever I need to repeat anything in the terminal. # Edit I sometimes add comments to commands via `# This‘ll do this and that` so that I can find the command by those keywords in the bash history.
Maybe I'm doing something wrong, but my bash history is missing many of my commands. I assumed it was due to poor handling of multiple open terminal windows and tabs.
Is there something you are doing so the different sessions don't clobber each other?
Re: Ask HN: Can I see your cheatsheet?
#159Re: Ask HN: Can I see your cheatsheet?
#160I keep a long cheatsheet for many-many-many years as a github gist: https://gist.github.com/sorokine/7b032ccb39514e2a64801f63d9e... (yes, it depends upon my dotfiles)