I once mixed up commands and results during a client demo
Last Thursday afternoon, I was demoing an automated workflow to a small team at a café in Hangzhou. The window had project files, run logs, and a client list open at once, and the light background made the dividers nearly invisible. I mistook a test email address for real data and nearly sent it to the client. That was when I realized that a tiny display problem on screen can mean hours of rework when someone has to sort everything by hand.
I’m not a terminal expert, and I got this wrong too: I originally assumed I had to change themes or buy new software. Later, I found that many terminals support a display option that draws borders by occupying one character cell. It doesn’t open another window or change the program’s contents; it simply draws a thin line around tabs, split panes, and some interfaces.
What it is, and who’s already using it
Put simply, it’s a terminal display setting that surrounds tabs or divided areas with a very thin character border. A terminal is essentially a place for displaying text and running programs, so the line you see is just drawn characters.
I know an independent consultant named Lin Zhou who does data analysis for two SaaS teams in Shanghai. When clients send daily reports, error logs, and query results at the same time, he gives each tab a different color and then enables these borders. What matters most to him isn’t how it looks, but how quickly he can confirm which dataset he’s working on after switching tabs. Compared with changing themes, this makes a smaller adjustment and is less likely to disrupt an existing workflow.
My replication attempt: almost free, 10 minutes to try
Cost: Usually ¥0, built into the terminal. Technical barrier: Finding “Settings” or the “configuration file” is enough; no coding knowledge needed. First step: Open the terminal you normally use, go to “Settings → Appearance” or “Profile,” search for an option containing “border” or the English word “borders,” then click preview.
Time: My first attempt took about 15 minutes, half of which was finding the setting. Once I confirmed it worked, maintenance took virtually zero time. If your terminal doesn’t have the option, you can update the software or search its official documentation for “cell borders.” You may also need a terminal that supports this drawing method. Not everyone needs it, and there’s no rush to try it now—making your current colors easier to distinguish may solve the problem too.
How I’d choose it by work stage
If I’m just starting out and mostly work in a browser and documents, I’d leave the terminal alone for now. When I need to process files in bulk or run simple commands, I’d give it a 10-minute test. If I already have one or two clients and regularly check logs or run data in the command line, I’d turn on borders first, then pick a theme color for differentiation and check the contents every time I switch tabs. If I’m scaling and several people share a server or I demo workflows frequently, I’d include borders in a shared configuration and keep a separate demo dataset that contains no sensitive information.
This isn’t a must-have tool. We can compare notes against a real work screen sometime; if you want, I can also help you judge whether it belongs in your workflow.