> Instead of doing one thing well, it does two things poorly.
It really doesn't. I think you just wanted something to say.
> It's not a very good window manager; when you use tmux you can't easily put a graphical window between two terminal screens
I think wanting to do that is your problem. I appreciate you may have your own insane use case, but mixing x/ptty makes no sense. Try just using your WM to switch to it.
> It's also not very good at keeping programs running. It can't survive a reboot, for example. It's possible to do that, and there's stable software that does it.
What are you even talking about? How is it supposed to know what your running and why you want to keep it running? Do you want your operating system suspend? Do you want to use docker pause/unpause? Then do. You can even script this stuff, which a number have done.
If your workflow unique to you then don't blame a tool designed for a different workflow
> > Instead of doing one thing well, it does two things poorly.
> It really doesn't. I think you just wanted something to say.
I'd say it does at least three things: terminal multiplexing, session management and copy/paste.
I switched away from tmux a while ago and now use DVTM for multiplexing and dtach for session management. DVTM delegates copy/paste to an external editor, but I've not used that functionality.
It really doesn't. I think you just wanted something to say.
> It's not a very good window manager; when you use tmux you can't easily put a graphical window between two terminal screens
I think wanting to do that is your problem. I appreciate you may have your own insane use case, but mixing x/ptty makes no sense. Try just using your WM to switch to it.
> It's also not very good at keeping programs running. It can't survive a reboot, for example. It's possible to do that, and there's stable software that does it.
What are you even talking about? How is it supposed to know what your running and why you want to keep it running? Do you want your operating system suspend? Do you want to use docker pause/unpause? Then do. You can even script this stuff, which a number have done.
If your workflow unique to you then don't blame a tool designed for a different workflow