instant.nvim VS zellij

maybe this https://github.com/jbyuki/instant.nvim.

For example, instant.nvim just shows where other clients are currently inserting. Assuming you don't do something daft like invite 500 strangers for a free-for-all, you shouldn't run into any problems.

You could also force your coworkers to use neovim and everyone can use https://github.com/jbyuki/instant.nvim (/j)

This has already been working in other forms for years, see for example https://github.com/mhinz/neovim-remote which is now more or less discontinued because the respective core implementation is indeed better longterm (again - this is a difference because this implements an unopinionated extension protocol that’s now easy to deliver with the refactoring efforts, not an opinionated packaged solution). A useful and fuller experience for the special case of remote editing would be https://github.com/jbyuki/instant.nvim for example, they also use this API principle you wanted to see - it’s just a nvim-server that is controlled remotely and you have an editor locally that acts as your direct interface (and you take this functionality into every other embedded solution!). And all of that is not just just somewhat fiddled solution but iterated solutions of the varying states of this feature implementation (on the path to neovim 1.0).

This plugin looks promising. https://github.com/jbyuki/instant.nvim

I've been keeping an eye on instant.nvim, though I haven't used it yet

Having a common set of tools already set up in different windows or sessions in Tmux or Zellij is obviously an option, but there is a subset of us ( 👋 ) that would rather just have fingertip access to our common tools inside of our editor.

Of my series of PRs, I suspect the third (i.e. https://github.com/zellij-org/zellij/pull/3043) is most likely to have an effect. But if it does it'd only be as a side effect unfortunately - my focus was on fixing lag with splitting of extremely long lines.

From what I saw while making my changes, that area of the code has a bunch more possible optimisations, but it's 'good enough' for me at this point so I'm not planning to continue pulling at the thread right now. If you wanted to look yourself, I left the script I used for benchmarking and profiling in https://github.com/zellij-org/zellij/issues/2622#issuecommen...

For this reason, and because I think the Zellij project is interesting, I currently use a combination of Alacritty and Zellij, as I consider the risk of OSC52 in my use case to be relatively low.

Hot to run a script on a keybind

Wait until you hear about Zellij

I entered a comment ( https://github.com/zellij-org/zellij/issues/1625#issuecommen... ) before I read your comment here. Please let me know if that is sufficient.

We do support attaching and detaching. And persisting sessions to disk (and indeed, to any serializable form) is being worked on: https://github.com/zellij-org/zellij/issues/575