-
dotfiles
My dotfiles: Experimental, ongoing configuration files, development environment and scripts for various Unix-like systems, text-based command-line applications and interfaces. (by kutsan)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
In your shell configs, you can check whether or not current shell is summoned inside vim/neovim process via $VIM_TERMINAL or $NVIM_LISTEN_ADDRESS environment variables and then, it's easy to launch tmux without or with a different session name (in order to prevent recursion, if you're using tmux as your top-level process). Check out this example for zsh and neovim. Use $VIM_TERMINAL instead of $NVIM_LISTEN_ADDRESS to support vim.
Use a floating terminal handler. Something like fterm or floaterm. You can use a terminal buffer or make more terminal buffers at ease but since they're child processes inside the current vim instances, they will be gone once you close the vim process. Not persistent but get the job done.
It sounds like you're describing reptyr which will let you repoint the TTY device(s) of a running process at a different TTY, so you can invoke vim and have it running, then suspend it, invoke tmux, and then use reptyr to move the vim session into a terminal within the tmux session.