[deleted]
Onivim 2 is a retro-futuristic modal editor
51–60 of 136 posts
Re: Onivim 2 is a retro-futuristic modal editor
#52It's unfortunate that some VS Code extensions, e.g. remote development extensions, can't be used in Onivim 2 due to license restrictions[1]. [1]: https://github.com/VSCodium/vscodium/issues/196#issuecomment...
Can any VS Code extensions be used in Onivim 2? Despite appearances, Onivim isn't a VS Code fork, it doesn't use Electron, and it's not written in Javascript-- it just happens to take substantial inspiration from VS Code's UI.
Re: Onivim 2 is a retro-futuristic modal editor
#53Does it really have INSTANT startup time (i.e. Sublime Text)? If it has, I'm interested. Was not able to find the trial though.
Yes, the startup time is amazing. You can build from source if you want to try it out without paying. I bought a license and I've been using it on and off for personal projects but it is still in development so don't expect everything to be perfect. Still really good though, actually feels like (is) Vim with a modern UI.
Re: Onivim 2 is a retro-futuristic modal editor
#54Earlier quoted context omitted.
> but implementing a vim backend is a monumental task if you intend to be compatible with existing vim plugins We skipped that and haven't implemented any vim backend at all! We use/made libvim[1], which is just the vim source, that we've essentially turned into a library. So its the vim code base with terminal UI stuff stripped out, and an interface added for us to hook into it. The README of that repo has some good…
It is my understanding that one of the initial driving forces behind NeoVim was to allow for easier embedding, such as what you appear to be doing here. If this is true, why did you decide to go with traditional vim rather than NeoVim? Additionally, since nvim lets you choose between Lua or Vimscript for configuration/extension, and I personally find Lua far more intuitive than Vimscript...
> If this is true, why did you decide to go with traditional vim rather than NeoVim?
Answered here [1].
> I personally find Lua far more intuitive than Vimscript...
One of the biggest motivating factors for the rewrite of Oni was the limitations imposed by Vim/Neovim of a terminal grid of characters in the rendering layer: “Neovim treats the visible screen as a grid of cells” [2]. This precluded implementing CodeLens amongst other things [3].
I’m also a fan of Lua — I’ve written a substantial amount of Fennel — but given Oni’s goals, revamping Vim’s rendering layer is of higher importance than Lua support, particularly since the VSCode extension ecosystem is being relied upon anyway. Onivim is designed as more of a direct challenge to heavyweight IDEs than as a substitute for Vim. I already switch between Vim and VSCode depending on requirements, but it’d be great to have the best possible support for modal editing in VSCode.
[1]: https://github.com/onivim/libvim#why-is-libvim-based-on-vim-...
[2]: https://onivim.github.io/docs/other/motivation#a-new-view-la...
Re: Onivim 2 is a retro-futuristic modal editor
#55What's most interesting for me here is Revery, the GUI framework. React-like, cross-platform, native-code, MIT-licensed. Yes, it's not using native widgets (so no built-in accessibility), but that might be fine in many cases.
I’ve actually been working on adding more support for native widgets in Revery, mostly focusing on macOS since thats my daily OS, but Windows too. You can now use native buttons and menus, and I’m looking into adding other native inputs (like text fields).
This is great news. Native text inputs have a lot of important affordances like navigation keys, selection, and spelling.
Re: Onivim 2 is a retro-futuristic modal editor
#56Earlier quoted context omitted.
> Also, there is VIM mode for VS Code, I guess. I feel like this is something said by people who are more invested in VS Code than vim. The main vim plugin for VS Code is straight trash.* It's slow, buggy, and unintuitive; while lacking the extensibility that vim has. At least IDEAVim, which has the same limitations of being built in another IDE, replicates enough of the common plugins to be pleasant. It's also worth…
> but implementing a vim backend is a monumental task if you intend to be compatible with existing vim plugins We skipped that and haven't implemented any vim backend at all! We use/made libvim[1], which is just the vim source, that we've essentially turned into a library. So its the vim code base with terminal UI stuff stripped out, and an interface added for us to hook into it. The README of that repo has some good…
Interesting. For once I am interested in compiling something to wasm. Thanks for the libvim link! :)
Re: Onivim 2 is a retro-futuristic modal editor
#57Put this color scheme in vim or neovim and get a couple plugins and you basically have 90% of this, but better
Re: Onivim 2 is a retro-futuristic modal editor
#58Earlier quoted context omitted.
> but implementing a vim backend is a monumental task if you intend to be compatible with existing vim plugins We skipped that and haven't implemented any vim backend at all! We use/made libvim[1], which is just the vim source, that we've essentially turned into a library. So its the vim code base with terminal UI stuff stripped out, and an interface added for us to hook into it. The README of that repo has some good…
It is my understanding that one of the initial driving forces behind NeoVim was to allow for easier embedding, such as what you appear to be doing here. If this is true, why did you decide to go with traditional vim rather than NeoVim? Additionally, since nvim lets you choose between Lua or Vimscript for configuration/extension, and I personally find Lua far more intuitive than Vimscript...
Seems they had trouble implementing that with Neovim[0]. Relevant reddit thread[1]
0: https://github.com/onivim/libvim#why-is-libvim-based-on-vim-...
1: https://www.reddit.com/r/neovim/comments/cdf36v/onivim2_chan...
Re: Onivim 2 is a retro-futuristic modal editor
#59Re: Onivim 2 is a retro-futuristic modal editor
#60I really wanted to like Onivim 2, but went back to Visual Studio code after supporting the creator on Patreon for a while. The last build and creator update was provided months ago for supporters. I also wanted to vote against the pricing model, because I think it should be a one time purchase. The creator and his company behind the editor tries to create a serious FOMO on likely customers. I considered it to be a re…
You can do a one-time purchase, IIRC it was ~$45 around a month ago when I purchased it. I wanted to buy outright instead of go the Patreon route.
As far as abandonment, I had a fairly subtle issue with it shortly after starting to try it, and on github I opened an issue and got help troubleshooting it in a day, we were able to identify the problem and there was a fix in the build the following day.