Text Processing (Grep/Sed/Awk)

Stop awk from tripping over fields with weird delimiters

🧩 The Challenge

Dealing with logs or CSVs that use something other than a standard space or comma is a nightmare, especially when fields contain embedded delimiters that break your column count. I’ve spent way too many nights manually counting indices only to have my script explode when a user puts a comma in a field.

💡 The Fix

Use the FS variable inside a BEGIN block to set your custom delimiter and handle those weird data structures without losing your mind. It keeps your field indexing clean even when the source file is messy.

awk -F'|' '{print $2, $4}' access.log
awk 'BEGIN {FS=","} {print $1, $3}' input.csv

⚙️ Why It Works

Setting the Field Separator (FS) explicitly at the start forces awk to treat your specific character as the break point, ignoring the default whitespace behavior. It completely clears up the confusion when you’re parsing data that wasn’t formatted by a sane human.

🚀 Pro-Tip: If you’re dealing with tab-delimited files, just use -F$’\t’ and skip the headache of trying to type an actual tab in your terminal.

Linux Tips & Tricks | © ngelinux.com | 8/6/2026