3 ms·
I sit beside a coworker who wrestles with tmux daily. He likes it, but it also frustrates him; it crashes semi-regularly, it sometimes locks out input when one
by barrkel 13y ago
I sit beside a coworker who wrestles with tmux daily.
He likes it, but it also frustrates him; it crashes semi-regularly, it sometimes locks out input when one program is spamming one of the tiles, and due to it intrinsic nature you can no longer select-copy large blocks of text with the mouse if you have any vertical splitters.
The lack of block text select-copy is alone enough to keep me away.
Most of the other benefits can be gotten with screen, with better reliability and performance. I use several customized .screenrcs for various tasks, to get started up quickly every reboot. But I don't run screen in every terminal because native scrollback buffer is too valuable.
- kawsper 13y ago> But I don't run screen in every terminal because native scrollback buffer is too valuable. I feel the exact same way. Scrolling inside screen is just a pain :(
- zaius 13y agoMac specific, but hold option+command when selecting and you can select in block mode.
- blantonl 13y agowow, thank you for that. That just made my use of tmux that much easier!
- barrkel 13y agoBlock mode selects don't know whether to wrap lines or not; most half-decent terminals keep track of whether wrapping was due to carriage return or hitting the last column. I do this all the time to e.g. select deleted files from a git status command so I can xclip paste the selection out through awk to xargs git rm (or rather, use some scripts which simplify the above). Similarly for rspec / cucumber test results to extract out the failures for use with $(<failures.txt) on repeated runs as I fix broken tests. I have a script that analyzes ruby stack traces, which I copy from the crashed session. All sorts of ad-hoc clickery, I rely on word wrap being detected consistently.