neovimcraft VS neovim-remote

I originally created https://neovimcraft.com in Svelte to learn how it works.

I found `$:` to be extremely confusing and full of weird quirks and completely turned me off to svelte entirely -- and decided to rip it out entirely for something simpler.

Runes seem like a clear improvement, but brings Svelte a step closer to React -- which hurts its appeal to me.

The difference between `let counter = $state(0)` and `const [counter, setCounter] = useState(0)` is near its initial value -- zero.

Does the community have a central repository of all plugins? I’ve used both this repo and neovim craft. If the latter creator has exposed the data via api that’s a fantastic plugin idea.

If you need plugins check out these websites. Awesome Neovim. and Neovimcraft.

Plus, you can take a look at awesome-neovim or neovimcraft for plugins that you may want to use. Lastly, you can also look at my config for some reference/guide. Hope it helps.

Always interesting to see how other people use Neovim and what they think is important! I found myself nodding my head to some of these and being completely unconcerned about others. In particular, I think that omnicomplete and completion in general is at a really good point for upstreaming. The landscape of completion sources hasn't been changing too much over the past few years, the problem is well understood, and the desirability is high (nvim-cmp is the fifth most starred Neovim plugin of all time).

Quick tip: Just think what plugins you need then search it on awesome-neovim and Looking at other configs will definitely help you. You can find other configs here at neovimcraft or dofyle.

I originally landed on https://neovimcraft.com because of https://vimawesome.com

I think you can make a PR to both github.com/rockerBOO/awesome-neovim and github.com/neurosnap/neovimcraft, looks like they accept PRs very often.

Very cool! I added it to https://neovimcraft.com/?search=codegpt

Notice that this script depends on mhinz/neovim-remote: Support for --remote and friends. (github.com). (nvr as you have notice). The full-path is required to make it work.

I am currently using https://github.com/mhinz/neovim-remote with this bit in my zshrc:

Since they are on different screens I cannot use a single neovim instance (I tried playing around with neovim-remote but seems like that's for the usecase of opening files in one instance from different terminals -- doesn't help). Due to multiple LSP instances changes in one file are not reflected in the other, e.g., file B imports some types from file A; I create a new type in A but since B's neovim instance is not aware of any change to the A file corresponding the LSP fails to see the new type.

This version includes `nv` binary which is [neovim-remote](https://github.com/mhinz/neovim-remote) but rewritten in Rust (I've did it out of boredom) also with interface similar to `page`.

Practical use case: when navigating in ANY terminal (or tmux) write a function that sends opened files to a single running neovim instance instead of spreading opened vim instances all around like neovim remote does, but works for any terminal

I see the integration with neovim is done via a separate plugin, did you think about adding support for neovim-remote?

Another way of doing what u/TheLeoP23 suggested is by using https://github.com/mhinz/neovim-remote . This way you have a single neovim instance and you can open it on different terminals and mantain your current workflow.