> There's only one .nvimrc to manage as opposed to also, tmux's file. Yes, this is definitely a trade-off. I tend to have a global .vimrc and .tmux.conf with

> There's only one .nvimrc to manage as opposed to also, tmux's file. Yes, this is definitely a trade-off. I tend to have a global .vimrc and .tmux.conf with some sensible default settings and on top of that, I do ad-hoc per project config files that have keybindings and other definitions unique to the project configuration. E.g. run a certain test suite with a keypress. The neat part in this is composability. The editor is just a component that you embed in your tmux. You might have other "components", such as a debugger or REPL or a file browser (ranger/midnight commander) in there too. This doesn't work as nicely if the "top level" is a text editor. I'm really fond of building these per-project ad-hoc "IDEs" out of terminal and editor windows because I work with a really diverse set of languages and tools and no single IDE or editor plugin suite would cover all my use cases without hurting the others.