Sorry, but it would be great to adapt it for the mobile layout.
Do you mean the website or are you talking about the book PDF?
Show HN: I wrote a modern Command Line Handbook
21–30 of 115 posts
Re: Show HN: I wrote a modern Command Line Handbook
#22Any alternatives to Gumroad in buying this?
Not for now. But I am happy to send you the PDF by email and receive a donation via PayPal if the reason is not to fund Gumroad. Just contact me on petr@stribny.name or @stribny on X.
Re: Show HN: I wrote a modern Command Line Handbook
#23It makes me wonder – what's that one command or concept you CLI vets wish you'd learned way earlier that totally changed your game, something that might be in that 'next 20%'? Curious about those 'aha!' moments!
Get really comfortable with find and grep. They’re incredibly powerful. perl -pe is way easier than awk.
Re: Show HN: I wrote a modern Command Line Handbook
#24Example pages here: https://drive.google.com/file/d/1PkUcLv83Ib6nKYF88n3OBqeeVff...
I consider myself reasonably proficient in the shell, but I learned something just from your sample pages (process substitution). Purchased!
Re: Show HN: I wrote a modern Command Line Handbook
#25Ahh yes, the lost art of UNiX sys admin always comes back.
Re: Show HN: I wrote a modern Command Line Handbook
#26It makes me wonder – what's that one command or concept you CLI vets wish you'd learned way earlier that totally changed your game, something that might be in that 'next 20%'? Curious about those 'aha!' moments!
One of my favorites from the book is to alias "xdg-open" to "open" because I never remember the command. So now I can just type "open X" to open a file system location or file in a normal GUI program when needed. It is a small thing but I use it a lot.
Something that I didn't put in the book because I learned it only recently is the use of "notify-send", aka you can send yourself a system notification from the command line or script (at least it workd for me in Gnome). For instance once a task is finished:
> echo "when finished send notification" && notify-send "system notification"
Pretty cool if you ask me!
Re: Show HN: I wrote a modern Command Line Handbook
#27Re: Show HN: I wrote a modern Command Line Handbook
#28This is excellent! Thank you for posting and best wishes for your success with this!
I'm teaching a class next year that'll have college-level students learning to use the command line and this looks perfect. Nowadays most 'learn the shell' resources online seem to focus on how to write scripts, without explaining how to use it interactively. Given this will be (for many) their first experience with a command line stuff like "type your command, then press enter", or "Up arrow to go back through your history" are a necessary foundation for them. Not to mention stuff like Job Control and using AI to help you create the more complicated commands that folks need to do - nicely done!
Plus, the book is inexpensive enough that they can still afford other resources too :)
Definitely gonna recommend this next year :)
Re: Show HN: I wrote a modern Command Line Handbook
#29Example pages here: https://drive.google.com/file/d/1PkUcLv83Ib6nKYF88n3OBqeeVff...
Hmm, the example page doesn't convince me, for example
> The diff utility can compare files and print their differences. If we pass it the result of ls commands, we can compare the contents of directories.
No, if you pass the output of ls commands, you might get an error because you'll pass a bunch of files to diff.
And last but not least there's
diff -r directory-a directory-b
Re: Show HN: I wrote a modern Command Line Handbook
#30Is your focus on older tools that tend to be on most machines and used in older shell scripts (e.g., find and grep), or on newer and upgraded tools (fd, fzf, rg) that developers install on their own machines, or both?