Hacker News Reader

Comment by andrewfromx | Hacker News Reader

exactly what I thought. Screen is there by default always and tmux would have to be installed sometimes. So maybe I should pick screen even though tmux is more modern and better? Tough choice really. I could see myself on some server someday without the time/option to install tmux and trying to learn screen in 5 mins.

View on HN

I use vim to be prepared for a new server, but do not stay with screen to be prepared.

I only once had a need (easy copy paste in terminal) to get tmux running on a server with no SSH, so I installed it.

For all other machines, which do not have tmux installed I use my local machine and SSH/MOSH with my local tmux. If there is a need to have a long running command on a server, I use tmux to detach the session, fallback to screen for detaching, fallback to SSH nohub

cheatmode is have a local statically compiled version of tmux ready to godmode servers you can SCP files to (all of em, if you've got ssh most likely)

That's what I'd do, if a server doesn't have screen/vim and sysadmins are being a nuisance.

Brilliant!

Unfortunately, the most recent tmux will not build statically.

I keep a pretty sparse toolset. vim+screen and always use them together even on my laptop.

So when I SSH into a box, I pretty much have my "full" toolset just as I would locally. For me, this is important.

That coupled with the fact I have my vimrc memorized, I'm pretty much good on all modern servers.

This is the approach I adopt as well. Customization is nice, but the basic tools offer a lot of functionality if you choose to learn and more so adopt them. Vim tiny some distros ship can be a problem though.

Reply on news.ycombinator.com