Taming My Terminal History: Customizing Bash History Behavior to Reduce Clutter

 Posted on 25 June 2026  |  3 minutes  |  565 words  |  Tom

Introduction to Terminal History

I’ve gotten pretty used to relying on my terminal history to recall previously executed commands. But let’s be honest, over time this history can become a mess with unnecessary entries, making it tough to find what I need. In this article, I’ll cover how to customize Bash history behavior to reduce clutter and improve productivity.

Understanding Bash History

Bash history is stored in a file specified by the HISTFILE environment variable, which defaults to ~/.bash_history. Each time a command is executed, it gets appended to this file. The HISTSIZE variable determines the maximum number of commands stored in memory, while HISTFILESIZE sets the maximum number of commands written to the history file. To view your current Bash history settings, you can use the following commands:

[Read More]
linux  bash  terminal  history 

Taming the Beast: My Favorite Aliases and Functions for Taming Long Commands in Bash

 Posted on 23 June 2026  |  4 minutes  |  642 words  |  Tom

Introduction to Aliases and Functions

I’ve been using Linux for years, and one of the things that’s really helped me streamline my workflow is using aliases and functions in Bash. These tools let you simplify long commands, reducing typos and making your life easier. In this article, I’ll share some of my favorite aliases and functions for taming long commands in Bash.

Creating Aliases

Aliases are basically shortcuts for longer commands. You can create an alias using the alias command followed by the name of the alias and the command it should execute. For example:

[Read More]
linux  bash  scripting  productivity 

Taming My Terminal History: How I Learned to Stop Worrying and Love a 10,000-Line Bash History

 Posted on 16 June 2026  |  2 minutes  |  396 words  |  Tom

Introduction to Terminal History

I’ve found myself dealing with a massive terminal history, spanning thousands of lines, more times than I can count. It’s a double-edged sword - having a record of all the commands I’ve run is great, but sifting through it all can be overwhelming. I decided to take control of my terminal history, and I’ve picked up a few tricks to make it more manageable.

Understanding Bash History

Bash history is stored in a file, usually located at ~/.bash_history. This file contains a list of all the commands you’ve run, in the order they were executed. By default, Bash will store up to 500 lines of history, but you can increase or decrease this by modifying the HISTSIZE variable in your Bash configuration file. Don’t bother with decreasing it, though - I’ve seen this go wrong when you need to recall a command from a few days ago.

[Read More]
linux  bash  terminal-history