instant.nvim VS vim-endwise

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

tpope/vim-endwise - Closes blocks like do-end etc.

Might be conflicting with coc, check this https://github.com/tpope/vim-endwise/issues/125

As you can see, I've commented it out. That is because as great as it is, it comes at an expense. First, it was often auto-completing words unexpectedly when what I was trying to do was create a new line. For instance, in Ruby files, I'd type do for a block and then hit enter to go the first line of the block's body. Instead, it would auto-complete do to does. Second, this overriding of the enter key was clashing with vim-endwise which I depend on for Ruby development.

Note, Tim Pope's endwise is also broken with Treesitter for similar reasons as noted here

What I really want is a nvim-ts-closeblock plugin that replicates Tim Pope's endwise plugin for Ruby when Treesitter is in effect.

I wish there were lua based version of https://github.com/tpope/vim-endwise.The plugin itself works great but if we add some kind of completion plugin, then things get dirty.There is a lot of issues like...

https://github.com/tpope/vim-endwise is a good plugin since it knows how to do this properly for several languages.