abduco

It can help to recognize that tmux combines three kinds of functionality: 1. process persistence; 2. client attachment; 3. view layout. If you don't like how tmux works, there are alternatives. I prefer Zellij [1]. (It also can be informative to take a peek at dtach [2] and abduco [3].) [1]: https://zellij.dev and https://github.com/zellij-org/zellij [2]: https://github.com/crigler/dtach and https://dtach.sourceforge.net [3]: https://github.com/martanne/abduco/issues/70

:term really changed the game for me. being able to run commands and then work with the output in other modes is so convenient. pair with neovim-remote[0], and it's pretty magical. i stopped using tmux because now all i need to do is open a terminal buffer in a new split to multiplex. i rarely used it for sessions, but use abduco[1] for that now when i find the need. [0]: https://github.com/mhinz/neovim-remote [1]: https://github.com/martanne/abduco

First of all, thanks for DVTM, it's really nice. The crashes I was referring to were seg faults, which happened seemingly at random, several months apart. If I had more useful/reproducible info I would've filed a bug report :( The unclean shutdown issue that I saw in the changelog seems to be https://github.com/martanne/abduco/issues/5 Before switching to dtach I was working around this by deleting stale sockets in my .xsession file: http://chriswarbo.net/git/warbo-dotfiles/commits/b182acaa1dc...

I'm all for experimenting with new ideas, however this seems to duplicate all the conceptual shortcomings I see in tmux. First of all, session support and terminal multiplexing are two distinct features which shouldn't be intermingled. What ever happened to the Unix principle of doing one thing and doing it well? My take on this problem is a combination of abduco[1] and dvtm[2]. Next a built in copy mode seems wrong, there is no need to implement vi(m) or emacs key bindings when you can make use of the complete editor. That is why dvtm uses my vim clone vis[3] as a filter: the terminal (scroll back) content is piped to $EDITOR and whatever the editor writes to stdout is kept in a register to be pasted in other terminal windows. Furthermore I think the completion menu should also be implemented as a standalone tool (using e.g. dmenu or slm