Hello, I use tmux for everything and I love it. I use tmux plugins `pain-control` and `sessionist` to preserve CWD while forking panes, windows, and sessions. I find it very handy.
Since a few months now, I've been using `neovim-remote` that keeps a single instance of neovim shared among the shells with matching environment variable `NVIM_LISTEN_ADDRESS`. This is very handy because combined with vim plugin `vim-rooter` allows me to open a terminal in the project's root I'm currently working on, and then issue more `vim....` command that will execute in the only vim open for that tmux window. Forking to another window, starts the setup again, where just the first `vim` command actually opens a vim instance, and all later `vim` commands for that same tmux window are "captured" by the now window-local-vim I've been looking to create my first tmux plugin in order to manage automatically `NVIM_LISTEN_ADDRESS` env var, the plugin, borrows heavily from `pain-control` and `sessionist` plugins. The plugin sort of works, it has one dirty corner: creating a new session (click here to see the involved code <https://github.com/daplay/tmux_nvr/blob/master/scripts/new_session.sh#L23-L26> ). As I can't use `-e` flag for `new-session` I've resorted to a very odd trick with `send-keys` that just feels wrong. I'm writing to check if anybody has faced a problem like this before or any other better approach. Thank you in advanced -- Daniel Baez -- You received this message because you are subscribed to the Google Groups "tmux-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/tmux-users/CAOsX1NNz%2BHD4YLVnJZbiijtNpFhuwzuO1%3Dv_zCcWtvFH6tOY_Q%40mail.gmail.com.
