Vim and tmux: separate editing from session management
A longtime Vim user describes separating editing, a REPL, and multiple project windows after adopting tmux.
The takeaway
Split the workflow when one tool is carrying too many responsibilities.
The context
The commenter previously used Vim as both editor and shell-like entry point, then adopted tmux for multiple windows and separating code from a REPL. The lesson is to identify the source of switching friction before assigning responsibilities to tools, not to prescribe a universal setup.
Steps worth trying
Editorial suggestions, not promises made by the original author.
- 01
Track editing, execution, and project switching for a day and identify repetitive window management.
- 02
Change one troublesome layout or shortcut first and expand the configuration only if it helps.
Where this applies — and where it may not
This is an experienced terminal user’s habit; additional tools have learning costs and may not suit every team.
From the discussion
“Now I use vim strictly as an editor/splitter.”
@exogenousdata · View source
Source: OpenIndex Hacker News dataset (ODC-By). Original content belongs to its authors. Summaries, translations, and suggested steps are AI-assisted editorial work. Read the sources; individual outcomes are not guarantees.