Shell Scripting / Bash Tricks

Stop letting variable names make your scripts a mess with local scopes

🧩 The Challenge

You ever write a function, change a variable inside it, and accidentally wipe out a global variable that the rest of your script depends on? It’s a total nightmare to debug because you’re looking at lines of code that didn’t even change.

💡 The Fix

Start declaring your internal variables with the local keyword so they stay contained within the function block. It stops name collisions dead in their tracks.

function update_config {
local config_path="/etc/app/config"
# Logic here won't touch the global $config_path variable
echo "Updating $config_path"
}

⚙️ Why It Works

Adding that local prefix tells the shell to allocate the variable on the stack for that function only, preventing it from leaking into the parent scope.

🚀 Pro-Tip: Always use it unless you explicitly want to change a global state.

Linux Tips & Tricks | © ngelinux.com | 10/15/2026