Building a Better Windows Terminal—Without Overengineering It
At some point, I realized I had somehow made it this far without ever setting up a terminal that was both pleasant to use and pleasant to look at. So I finally fixed that.
A terminal is one of those tools developers touch all day, every day. A good setup is not just eye candy—it removes friction from navigation, command history, file search, and everyday Git work.
This post walks through the practical Windows 11 setup I ended up with. It is fast, clean, and useful without sending me too far down the dotfiles rabbit hole.
My Starting Point
If you are also running Windows 11, the following PowerShell snippet will print a quick summary of your hardware:
$cs = Get-CimInstance Win32_ComputerSystem
$cpu = Get-CimInstance Win32_Processor
$os = Get-CimInstance Win32_OperatingSystem
$gpu = Get-CimInstance Win32_VideoController
$disk = Get-PhysicalDisk
@"
Model: $($cs.Manufacturer) $($cs.Model)
OS: $($os.Caption) $($os.Version) (Build $($os.BuildNumber))
Architecture: $($cs.SystemType)
CPU: $($cpu.Name)
Memory: $([math]::Round($cs.TotalPhysicalMemory / 1GB)) GB
GPU: $(($gpu.Name -join '; '))
Storage: $(($disk | ForEach-Object { "$($_.FriendlyName) $([math]::Round($_.Size / 1GB)) GB" }) -join '; ')
"@
1. Start with Windows Terminal
If you are still using the old Windows Console Host, I strongly recommend installing Windows Terminal. It gives you tabs, split panes, proper font rendering, profiles, and a much better experience overall.
Install it with winget:
winget install --id Microsoft.WindowsTerminal -e
Once it is installed, press the Win key and search for Terminal. You can also launch it from PowerShell by running:
wt
2. Add the CLI Tools That Actually Matter
I use Scoop to install command-line tools. It keeps installations lightweight and makes updating or removing utilities painless.
These are the four tools in this setup:
- lazygit: A terminal UI for Git. It puts staging, commits, diffs, branches, rebases, and other common operations in one interface. It is especially handy when you do not feel like reconstructing a long Git command from memory.
- fzf: A general-purpose fuzzy finder. It can filter command history, file lists, directory names, and almost any other text-based input. In this setup, Ctrl + R searches command history, while Ctrl + T searches for files.
-
fd: A fast, user-friendly alternative to
find. For example,fd mainrecursively searches the current directory for names containingmain. -
zoxide: A smarter replacement for
cd. It learns which directories you use based on “frecency”—frequency plus recency—and lets you jump to them with short, fuzzy matches.
Install everything with Scoop:
scoop bucket add extras # lazygit lives in the extras bucket
scoop install lazygit fzf fd zoxide
fd works immediately, and lazygit does not need
any urgent configuration. The two tools we need to wire into PowerShell
are fzf and zoxide.
3. Wire Up fzf and zoxide
First, install PSFzf, which integrates fzf with
PowerShell:
Install-Module PSFzf -Scope CurrentUser
PowerShell may ask whether you want to install the NuGet provider or trust
PSGallery. Enter Y when prompted.
Next, create and open your PowerShell 7 profile:
$profileDir = Split-Path -Parent $PROFILE
New-Item -ItemType Directory -Path $profileDir -Force | Out-Null
if (-not (Test-Path $PROFILE)) {
New-Item -ItemType File -Path $PROFILE -Force | Out-Null
}
notepad $PROFILE
Add the following configuration:
# fzf: fuzzy file and command-history search
Import-Module PSFzf
# Ctrl+T: fuzzy-select a file from the current directory
# Ctrl+R: fuzzy-search command history
Set-PsFzfOption `
-PSReadlineChordProvider 'Ctrl+t' `
-PSReadlineChordReverseHistory 'Ctrl+r'
# Use fd as the default fzf backend: fast, hidden-file aware,
# and smart enough to stay out of .git
$env:FZF_DEFAULT_COMMAND = 'fd --type f --hidden --exclude .git'
$env:FZF_CTRL_T_COMMAND = $env:FZF_DEFAULT_COMMAND
$env:FZF_DEFAULT_OPTS = '--height 45% --layout=reverse --border'
# zoxide: smart directory jumping
# Keep this at the end of the profile
Invoke-Expression (& { (zoxide init powershell | Out-String) })
Save the file, then reload your profile:
. $PROFILE
Your everyday terminal workflow now looks something like this:
z leaf # Jump to the best-known directory matching "leaf"
zi # Pick a previously visited directory with fzf
Ctrl+T # Find a file and insert its path into the command line
Ctrl+R # Search through command history
fd main # Find names containing "main"
fd -e cpp # Find every .cpp file
fd -t d build # Find directories named "build"
lazygit # Launch the Git TUI inside a repository
At this point, the terminal is already useful. Now we can make it look like something we actually want to keep open all day.
4. Make It Look Good with Oh My Posh
I used Scoop again to install Oh My Posh, along with the Meslo Nerd Font:
scoop install oh-my-posh
oh-my-posh font install meslo
Open Windows Terminal settings with Ctrl + ,, then go to Profiles → Defaults → Appearance and change the font face.
I went with MesloLGM Nerd Font Mono, but this is entirely
personal preference. Any Nerd Font with the glyphs you need should work.
Before making the change permanent, you can preview a theme in the current PowerShell session:
$ompTheme = 'jandedobbeleer'
oh-my-posh init pwsh --config $ompTheme | Invoke-Expression
You can browse the available themes in the Oh My Posh theme gallery.
Once you have picked a theme, open your profile again:
notepad $PROFILE
Add the Oh My Posh initialization immediately
above the zoxide initialization:
# Minimal Git-aware prompt
oh-my-posh init pwsh --config "jandedobbeleer" | Invoke-Expression
# zoxide: smart directory jumping
# Keep this at the end of the profile
Invoke-Expression (& { (zoxide init powershell | Out-String) })
Save the profile and reload it one last time:
. $PROFILE
And that is it—you now have a terminal that works as well as it looks.
Final Thoughts
This is only my personal baseline. A good-looking terminal is nice, but usability is the part that actually matters. The best setup is the one that fits your workflow and then gets out of your way.
Customize what helps. Skip what does not. Try not to turn maintaining your terminal into a second job.
Hope this helps!
评论
发表评论