Hello!
I am pleased to announce a new version of my CLI text processing with GNU awk ebook. This book will dive deep into field processing, show examples for filtering features, multiple file processing, how to construct solutions that depend on multiple records, how to compare records and fields between two or more files, how to identify duplicates while maintaining input order and so on. Regular expressions will also be discussed in detail.
Book links
To celebrate the new release, you can download the PDF/EPUB versions for free till 06-April-2025.
Or, you can read it online at https://learnbyexample.github.io/learn_gnuawk/
Interactive TUI apps
- 80+ exercises: https://github.com/learnbyexample/TUI-apps/blob/main/AwkExercises
- Brief tutorial: https://github.com/learnbyexample/TUI-apps/blob/main/AwkTutorial
Feedback
I would highly appreciate it if you’d let me know how you felt about this book. It could be anything from a simple thank you, pointing out a typo, mistakes in code snippets, which aspects of the book worked for you (or didn’t!) and so on.
Happy learning :)
I’m not expert in sed or awk. I always have to Google. For me though, it’s generally that you can do a great deal in just one line of awk or sed. They’re standard on any Linux distribution I’ve ever used. When building out pipelines, scripts that you want run from an installer you built post install and when removing, sed and awk rather than needing python.
All really nice when you have strict configuration management and versioning and there’s something deployed but it doesn’t have the python packages installed that would make it easy in python and you can’t just pip install it on hundreds+ of computers without going through a process of approval and building a new tagged version release but sed/awk/etc can do the job. If it’s hard enough, python and whatever packages you can install. If simple enough to do in a small bash script, no python just what’s standard in your Linux distro