4 ms·

I didn't try it. But I surfed the website and watched the animations. I am using stock Neovim on the console. For completion I switched to nvim-cmp https://git

I didn't try it. But I surfed the website and watched the animations. I am using stock Neovim on the console. For completion I switched to nvim-cmp https://github.com/hrsh7th/nvim-cmp https://github.com/hrsh7th/nvim-cmp. Onivim also provides (based on the screencasts) completion. Do they leverage their own coded completion engine or are they using nvim-plugins and only render the UI over this completion? My point is there will always be an impedance mismatch between functionality provided by plugins compared to what a UI provider thinks has to be coded in their respective implementation.

boudin 5y ago
Seems that the idea is to implement vscode APIs and use the vscode plugin host and backend system for extensibility.
- ctenb 5y ago
  Why not just write a Vim plugin for VSCode then though? Which already exists.
  - maattdd 5y ago
    Performance
mcjiggerlog 5y ago
It's on the homepage - they aim to support the full VS Code extensions API and that is how they power language features like completion. I've been keeping an eye on onivim for a long time and think it has a lot of potential. Last time I tried it it still had too many rough edges to try and use as a daily driver, though.
3np 5y ago
Neither. > Onivim is capable of loading VSCode extensions
riedel 5y ago
I have a onivim2 licence and thus try it from time to time. Speed etc is impressive. Currently I think it is about getting the last 20% done and development has been slowing down a bit. Really hope this get done. I still cannot really get a grasp on how viml and vscode extensions might interplay. It is btw interesting to note that onivim 1 was neovim but the author decided that it was better to wrap the vim source code.