My Simple Pacman.conf for a Better Arch Experience It’s the small quality-of-life tweaks that make using a minimal OS like Arch Linux truly joyful.

👋 Hey everyone,

There’s a unique satisfaction that comes with running a lean, mean Arch Linux machine. You build it from the ground up, and every package is there because you chose it. But after the initial thrill of a successful installation, the daily routines kick in. For me, that’s running pacman -Syu almost every morning. While I love how powerful pacman is, I have to be honest: its default output is a bit harsh on the eyes. Just a wall of white text that makes it hard to quickly see what’s really going on. This week, I decided to finally fix that.

My Goal This Week 🎯

My goal was simple: make my daily system updates less of a chore and more of a pleasure to look at. I wanted to be able to glance at the output and immediately understand which packages were being upgraded, their old and new versions, and their download sizes, all without straining my eyes. The solution had to be simple, clean, and stick to the Arch philosophy of using built-in tools effectively.

The Process & The Code 👨‍💻

The magic, as it often is in the Linux world, lies within a single configuration file: /etc/pacman.conf. This file controls the behavior of the pacman package manager. After a bit of digging—mostly just reading the well-commented file itself—I found the exact lines I needed.

The fix involves uncommenting (removing the # from the beginning of the line) just two options under the [options] section. I also made sure that parallel downloads were enabled, which is a huge time-saver you should definitely be using.

Here are the changes I made to my /etc/pacman.conf:

# /etc/pacman.conf

[options]
# Misc options
#UseSyslog
Color               ## This is the key for colorful output!
#NoProgressBar
CheckSpace
VerbosePkgLists     ## This formats the package list beautifully.
ParallelDownloads = 5 ## Bonus: Speeds up downloads significantly.

All you have to do is open /etc/pacman.conf with your favorite text editor (like sudo nvim /etc/pacman.conf) and make these simple adjustments.

Hitting The Wall 🧱

The wall I hit wasn’t a bug or a complex technical problem. It was a wall of plain, monochrome text. Every time I ran an update, I’d be met with a list that was hard to parse quickly. Trying to scan which packages were major or minor updates, or just trying to find a specific package in the list, felt inefficient. It’s a small friction point, but when you interact with the terminal multiple times a day, those small frictions add up and disrupt your flow. It felt like I wasn’t taking full advantage of the modern terminal I was running.

The Breakthrough Moment ✨

The breakthrough was realizing the solution was already in the configuration file, just waiting to be enabled. I didn’t need a wrapper script or a fancy external tool. The Arch developers had already provided the functionality.

The moment I saved the file and ran my next pacman -Syu, the difference was night and day. The package names were colored, version numbers were highlighted, and the entire list was presented in a clean, tabular format. It was one of those “Why didn’t I do this years ago?” moments. This simple change transformed a mundane task into a visually pleasing and informative process. It’s a testament to the thoughtful design of Arch’s core utilities.

📚 Recommended Resource

Speaking of mastering the terminal, if you want to go from a beginner to a command-line pro, I can’t recommend “The Linux Command Line” by William Shotts enough. This book is a comprehensive and incredibly accessible guide to the shell. It doesn’t just teach you commands; it teaches you the philosophy behind the command line. It covers everything from basic navigation to powerful shell scripting. Even after years of using Linux, I still find myself referring back to it. It’s the perfect companion for anyone serious about making the most of their Linux system. Amazon

Key Takeaways 📚

  1. 💡 Read the Configs: Often, the features you want are already built into your tools, just disabled by default. Take a few minutes to read through the configuration files of the programs you use daily.
  2. ⚙️ Small Tweaks, Big Impact: You don’t need complex solutions to dramatically improve your workflow. A two-line change made my daily updates faster and more enjoyable.
  3. 📚 Aesthetics Aren’t Frivolous: A clean, readable, and visually appealing workspace reduces cognitive load and makes work more pleasant. This applies just as much to the terminal as it does to a physical desk.

Thanks for Following ☕

I hope this simple tweak helps you enjoy your Arch Linux experience even more!

☕ If you found this guide helpful, you can Buy Me a Coffee! Medium Etsy LinkedIn Read More

What’s your favorite ‘must-have’ tweak in your pacman.conf or shell setup? Share it in the comments!