41–50 of 115 posts
Electron frontend is precisely the thing I really don't want from a tool like vim...
People here claim this is a lot better for performance. I've no personal experience to verify this.
People mention it is better than Atom due to how it leverages Electron which is nice but still, what is the value proposition of this IDE?
It says it's powered by React and (presumable) Electron - does it have the same kind of issues that Atom does? Can it open big files, how responsive is it, etc. How do plugins work? Do neovim plugins work out of the box with Oni, do you have to write a wrapper, or are they completely incompatible? This is really the make or break part of it.
It says it's powered by React and (presumable) Electron - does it have the same kind of issues that Atom does? Can it open big files, how responsive is it, etc. How do plugins work? Do neovim plugins work out of the box with Oni, do you have to write a wrapper, or are they completely incompatible? This is really the make or break part of it.
By default it doesn't load your init.vim, but if you change that flag in the config it will behave exactly like your regular neovim install (since that is in fact exactly what it is: a very light canvas renderer wrapped around neovim). I have been using it for a couple of weeks with all of my vim plugins with no issues (ctrl-p, buffer gator, easy motion, etc). Edit: it's worth pointing out that while the rendering is…
Looks great. Two questions: 1. I wonder though why you/team didn't opt for extending the vim emulation - via a plugin - on VS Code. Did the exposed API limit you from doing so? Edit: Having used the extensions of VSCode, I am wondering if that is the case. 2. Does it support installation of sublime/atom/vscode plugins?
As a developer of the VSCodeVim plugin, Oni is a great inspiration and we are hoping they pave the way for the Neovim API (which is starting to mature). We have started using neovim for a few things, the command line for example. So while we have started getting our feet wet, hopefully something like Oni (or Oni) replaces us...soon :)
Thanks for contributing to the VS Code ecosystem.
I've been using Oni for the last few weeks as my daily driver (I liked it so much I signed up as a monthly sponsor), and here's my take on it: It's a fairly new project, but it's under _very_ active development. There's an excellent community building around it and I think we will be seeing some really great progress over the next year. That said, it isn't anywhere close to feature parity with vscode, but the value p…
Code is a great editor/IDE and has a huge amount of development backing and now a pretty large market share as well, which means inertia. But the vim bindings for it are just garbage. They are slow, make the editor feel sluggish, they don't work "quite right", etc.
No kidding this sparked some inspiration, but now I'm just going to have to either look at Oni and be jealous forever until VSCode catches up (if it ever does), or switch to Oni and end up missing out on all the features and inertia of VSCode :/
Hopefully the work that goes into this newer editor will spark some inspiration and get some of the work offloaded to libraries which VSCode can use as well.
Does it work with vim plugins? How much of my pre-existing vim configuration can be transfered onto oni? It's currently about 500-1000 lines in .vimrc and ≈50 3rd party plugins.
Does it work with vim plugins? How much of my pre-existing vim configuration can be transfered onto oni? It's currently about 500-1000 lines in .vimrc and ≈50 3rd party plugins.
Pretty much 100%. It's a regular instance of neovim, just with an Electron UI around it. I've had no issues with my .vimrc at all.