libvim

It's not that cut and dry. See https://github.com/onivim/libvim#why-is-libvim-based-on-vim-... It's mostly due to their build system.

I think perhaps libvim is like that? https://github.com/onivim/libvim

Onivim might not be for you :) But our project under the hood, libvim [1], might be useful for you to start (if it's easy to create bindings from C in Go). There's a cool non-Onivim usage of it called Paravim [2] (and the same author also used it for Vim-Cubed [3]) - [1] https://github.com/onivim/libvim/blob/master/src/libvim.h - [2] https://github.com/paranim/paravim - [3] https://github.com/oakes/vim_cubed

Thanks for checking out the project! This is one of the biggest pieces feedback we've received both the tabs / splits in particular [1], and the more general issue of broader Vim compatibility [2]. We actually use a forked Vim implementation under the hood (libvim [3]) - as the modal-editing engine. So Onivim, in theory, _could_ support everything. The main issue is 'wiring up' features from libvim to our front-end. We'll be focusing on this in our next milestone (July-Sep) - with the high level goals of supporting more traditional Vim workflows, Vim tab support, along with VimL plugin support and init.vim/vimrc compatibility. Ultimately it's a prioritization problem - so having feedback like yours is really helpful, so that we can focus on the right priorities for that work. - [1] https://github.com/onivim/oni2/issues/592 - [2] https://g

https://github.com/onivim/libvim#why-is-libvim-based-on-vim-... Guts of it is that Neovim didn't play nicely with their OCaml build and Vim did. Rather than invest time in working through the problem, they went ahead with Vim but remain open to supporting Neovim.