vimpager. Set vim as your pager. I love reading man pages in syntax-colored vim glory.
'most' will colorize bash output as well (it's strictly a pager, in the pg / more / less / most continuum).
A hack for in-place editing, for old school sed (no -i):
sedi(){ case $# in 0) echo usage: sedi cmds file;; 2) sed -an ' '"$1"'; H; $!d; g; w '"$2"'' $2;; esac; }
It, along with other readline functionality, shell functions, substitutions, expansions, scripts, and the bazillion utilities are what make Linux (and Unix) shell so much more than just "it's like DOS, right?".
Yeah, kind of, in the same way that ... a cross between a Prius, a Mack Truck, an Lamborghini, an F-16 fighter, a helicopter, and a freight train are like a pushcart. It's an interface that helps you manage your computers, the things on them, and the things they're connected to. It's also a hugely efficient and effective way to process information and issue commands and controls in a useful way.
Unless you only use GPL software, there's no reason to not use tmux these days. Well, maybe if you're on HP-UX or something.
However, it's not true that screen has no advantages over tmux. Each program has its own strengths and weaknesses. For instance, screen is scriptable via its Lua bindings, tmux is not. Screen has zmodem support built in, tmux does not. There are probably many other examples, since screen has a bazillion features which have been developed over decades, while tmux is relatively new (and its developers don't seem to care to duplicate every one of screen's features).
It's certainly true that screen does have tons of small old features... but I sort of swept that in with "unless you're using HP-UX or something." zmodem support isn't exactly relevant to the overwhelming majority of programmers, but yes, I admit these things are still relevant to a few niches.
I'm not sure if tmux is scriptable to the same extent that screen is via screen's Lua bindings, as the latter probably exposes many of screen's internals, while scriptability of tmux is limited to what you could do with its command line arguments. I haven't researched the matter, though, so I may well be wrong.
I often have to fix servers that are not from own group, so all my knowledge is honed around tools that i can find anywhere.
# put this in your .screenrc
escape ^Oo escape ^\\It works because I have my shell configured to use vi mode for command line editing.
screen, pdsh,
perl -pi -e 's/find/replace/g' *.txt
redis-cli's new ability to have piped in data be the last argument of a command.
vim -o file1.txt file2.txt file3.txt (opening multiple files with vim)
Using vim instead of less as a pager: cat file.txt | vim -