If you have any suggestions or criticisms, feel free to comment them.
Being plain text, it’s much easier to read on a wide screen, or on something without line wrapping.
would you upload this on github?
Done? I’ve never uploaded to GitHub before, and I was just doing what I thought I should do. I’ll do my best to keep it updated with the version on my website.
https://github.com/ordinarybyte/linux_cheat_sheet
Is there a way to make GitHub automatically detect changes to the file at cerium.cc and update the repo? Or do they not allow that? I know a scheduled script would be able to work but I don’t really want to have to run it myself.
Oh. My. Gosh. I love this. Thank you. And thank you for being
--verboseabout the provenance and history of the document. And big big thank yous for the Internet Archive links. Bravo.I’ve been using Linux for decades and I bet that’ll still come in handy.
At the end, in redirection,
<<: that’s not how here-documents work. The example gives the impression it will read the given file up until “STOP”, but in reality the shell expects you to keep writing your here-doc until you write “STOP” and then feeds it to the program as if it were all on stdin. I don’t think wc even does anything with the stdin if you give it a filename… Note that variable expansion will happen in here-docs, so it’s a bit different than a simplecat. Also look into here-strings. And process substitution, I find that quite handy.Interesting compilation, there is cheat.sh, tldr and others though
I made this just as much for me as I did for others. Writing things down myself really helps me memorize them.
Wow. I’ll definitely avoid Linux now. I had heard Linux was supposed to be easy to use now.
This is really nice!
Cool, thank you!
Thanks for all the feedback! I’m much happier with it now, and I’ll probably continue to make small changes over time.
This is fantastic. Just at a glance I already learned something new! Definitely keeping this for reference.
