Our great sponsors
-
Thanks for trying it out and sharing your feedback, appreciate it!
> However, I really don't like the fact that there is no way to navigate tabs using vim's commands.
There's a related feature request here: https://github.com/onivim/oni2/issues/3673
> I also find the VSCode similarities distracting and it seems to be causing confusion to would be investors of this due to the assumption it's some branch of it as opposed to a completely new editor.
I agree, this is consistent feedback we get... There's a ton of potential to have a built-for-modal-editing UX that we're missing at the moment.
> Finally, is there a way to remove the system bar on the top in the configuration? I can toggle most elements of the UI but that system bar is visible even in zen mode and I never use it in any text editor with support for keyboard driven commands.
Yes, there is a `window.menuBarVisibility` configuration setting: https://onivim.github.io/docs/configuration/settings#layout
-
> 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...
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
It'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...
-
Is it better than (the AFAIK newer) https://github.com/asvetliakov/vscode-neovim ?
-
> Can any VS Code extensions be used in Onivim 2?
Yes, this is basically the entire point of Onivim. https://open-vsx.org/
-
If you like Kak and are vaguely familiar with Sam I suggest trying out vis:
> Vis aims to be a modern, legacy-free, simple yet efficient editor, combining the strengths of both vi(m) and sam.
https://github.com/martanne/vis
"Differences from Kakoune": https://github.com/martanne/vis/wiki/Differences-from-Kakoun...
-
Yep! You can find the MIT repo here: https://github.com/onivim/oni2-mit
I actually never thought of it in the context of Id Software, that’s an interesting comparison!
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
>It requires making my own syntax files for every language I use, and starting or opening a new language now needs to begin with configuring this. Not really looking forward to such a future.
Why would you need this (unless your language is not in https://github.com/nvim-treesitter/nvim-treesitter#supported... ?)