Hacker News Reader

What workflow involves opening hundreds of shells every day? Like, I've got a half dozen shells open at any given time, and sometimes I gotta refresh or reboot, but even on my worst day in looking at two dozen.

How do you get to hundreds?

View on HN

Temporary splits to run code close to the editor, tmux popups (they open lazygit or file manager on top of the current tab). Debug runs, where I want to preserve their output for some time, so I keep them in separate tabs.

I use a lot of short-lived terminals. I have zsh+foot configured so that ctrl+shift+n opens a new terminal with the same current directory, so when using Vim, that's as fast as putting Vim in background, but I can tile both windows easily.

I never have more than a one or two dozen terminals at a time, but I definitely open hundred of short-lived ones.

Why? You've said you do but not why you do? Why not leave a terminal open?

Why would I leave it open once I'm done with the task for which I opened the terminal?

Reply on news.ycombinator.com