Creating a Modern Terminal Setup

I've been tweaking my terminal for years. There were periods where I spent more time configuring my prompt than actually writing code (the classic trap). But after enough iterations, I landed on a setup that's fast, useful, and doesn't require me to remember arcane config syntax every time I touch a new machine.

Audio Briefing• Voice: Google Cloud Journey-F

0:00 / 0:00

Part of a Series

Modern Linux & Terminal Mastery Series

Part 2 of 4

Part 1:How to Add a Directory to PATH in Linux (Permanent Fix)

Part 2:Creating a Modern Terminal Setup

You are here

Part 3:Ubuntu Server Security Fundamentals

Part 4:Unwritten Rules of Terminal Programs

Up next:Ubuntu Server Security Fundamentals

The Foundation

24-bit color. If your terminal still looks like a 1980s terminal, fix this first. Most modern emulators support it out of the box, and the difference is noticeable the moment you open a colored diff or a lint output.

Infinite scrollback. Nothing worse than a complex command scrolling off-screen right when you need to reference it. Set your scrollback to unlimited or a very large number.

Autocomplete. Fish shell does this natively. With Zsh you need a plugin. Either way, once you get used to tab completing git branches and file paths, going back to a bare shell feels broken.

Pick an Emulator

iTerm2 on macOS, Kitty or GNOME Terminal on Linux. GPU acceleration matters more than you'd think: it keeps the terminal responsive when you're running something that spews logs at high speed.

Swap Your Shell

Default bash is fine but limited. Zsh with a framework or Fish out of the box gives you autocomplete, theming, and plugin management without fighting .bashrc conventions from 1999.

Set Up a Prompt

Starship is my pick. It works across shells, shows Git status, Python version, Node version, and it's fast. No perceptible delay on render.

Where People Get Stuck

The dotfile rabbit hole is real. You'll find a cool prompt theme, then a plugin that depends on another plugin, and suddenly you're reading a 200-line .zshrc trying to figure out why git status takes two seconds.

My rule: if a terminal customization takes more than 10 minutes to configure, it better save me 10 minutes a week or it gets cut. By that standard, most prompt themes and half the popular Zsh plugins don't make the cut.

What Actually Survived

A minimal Starship prompt showing Git branch, Python version, and exit code.
zsh-autosuggestions: grays out recently used commands as you type. Saves more keystrokes than anything else I've installed.
zsh-syntax-highlighting: red text for invalid commands before you press enter. Catches typos constantly.
A handful of aliases that I actually use. Not the 50-line alias dump from a blog post I copied once and never edited.

Your setup should reflect how you actually work, not how some blog post said you should work. Start with the three things above, use them for a week, then decide what's missing.

Terminal Series

Unwritten Rules of Terminal Programs: Why q quits, Ctrl-C cancels, and other conventions
Why Pipes Sometimes Get Stuck: Buffering Explained: How stdio buffering breaks pipelines
Creating a Modern Terminal Setup (this post)

Free Developer Tool: AI CLI & Terminal Output Cleaner

Sharing terminal outputs, compiler logs, or AI CLI traces in GitHub issues or documentation? Use our free AI CLI & Terminal Output Cleaner to strip ANSI escape codes, prompt characters, and timestamps instantly.

Clean Terminal Logs for LLMs & Documentation

When sharing terminal outputs into AI chat prompts, bug tickets, or documentation, ANSI escape color sequences, timestamps, and shell prompts often corrupt the formatting. Use our interactive cleaner below to strip ANSI codes, line numbers, and shell noise instantly:

Frequently Asked Questions

Oh-My-Zsh executes hundreds of synchronous shell scripts on every prompt redraw, causing noticeable 200-500ms lag in large Git repositories. Starship is compiled in Rust, renders asynchronously in parallel with sub-10ms latency, and shares identical configuration across Bash, Zsh, and Fish shells.

GPU acceleration offloads glyph text layout and viewport redraws to the graphics pipeline via Metal, Vulkan, or OpenGL. This eliminates terminal lag and frame drops when streaming large test outputs or build logs, while keeping keyboard input latency under 5ms.

Use declarative dotfile managers like chezmoi or maintain a bare git repository in $HOME with an alias (dotfiles='git --git-dir=$HOME/.cfg/ --work-tree=$HOME'). This eliminates external symlink scripts and allows simple git push/pull syncs across machines.

Zsh remains the industry standard due to POSIX compliance, ensuring that copied bash snippets and enterprise CI scripts execute without modification. Fish offers the fastest out-of-the-box autocomplete and syntax highlighting, but requires running bash explicitly for non-POSIX shell scripts.

Engineers benefit most from Rust-based replacements: eza (replaces ls with git status markers and tree views), bat (replaces cat with syntax highlighting and line numbers), ripgrep (blazing fast regex search replacing grep), and fzf (fuzzy interactive shell history search).