> Also notable is if you upgrade you can't re-attach to sessions started by an older version of screen.
Last time tmux was updated someone pointed out this surprisingly obvious way to reconnect to and old server after an update:
/proc/${pid_of_tmux_server}/exe attach
> I would imagine you could to the same for screen.
I'm not so sure. According to the Arch Linux announcement from 4.2.0, the switch screen made was from named pipes to sockets [1]. Presumably this implies they stripped out support for the former in the latest version, which would mean the announcements are valid and it's therefore impossible to reattach an old session.
Although, it didn't matter to me. I usually read release announcements regularly before updating my distribution. It doesn't guarantee that I catch everything (or that I even remember to check), but it does limit the number of surprises I encounter. Completely closing off a few screen instances and restarting them wasn't a huge issue, but it was a mild annoyance.
For screen? I didn't catch that since it appears the comment was referring to using a similar method for tmux. I can see how that would work, but the primary concern I was addressing was that in all likelihood, users are bound to update screen--and to their surprise find that they can't reattach.
Keeping the old binary would make sense, though. Evidently that possibility was lost on me. My mistake.
Last time tmux was updated someone pointed out this surprisingly obvious way to reconnect to and old server after an update: /proc/${pid_of_tmux_server}/exe attach
I would imagine you could to the same for screen.