Developers struggle to use tmux across remote and local workflows
Developers who rely on tmux for persistent SSH sessions find its controls and mouse behavior difficult to configure, and using it alongside a local tmux session can make remote work awkward. They also want to keep persistent sessions while using the tabs and panes in GUI terminals or editors that lack tmux control-mode support. A standalone client or launcher could improve much of this workflow, though it cannot add native support inside other applications.
For developers who use tmux over SSH. Mentioned from Feb 2020 to Jun 2024 on GitHub and Hacker News.
5 different people described this problem in 4 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.6/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
It’s the arcane shortcuts and the weird way it seems to handle most things (trying to get the mouse working is a bloody nightmare and it regularly borks the terminal)
The problem is that because I use tmux so heavily locally, using it remotely is a pain in the ass. My normal workflow is either to be sitting in front of my Linux machine, or SSH'd to it (from a Windows laptop). Tmux makes the transition between those two seamless. But nesting tmux doesn't work
rkangel on Hacker NewsJun 2024
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks