openvsx VS libvim

It is incredibly difficult to assess the quality of projects in depth.

I tried doing this for Open-VSX extensions for handling justfile:

https://open-vsx.org/?search=justfile&sortBy=relevance&sortO...

  2.4k nefrob.vscode-just

Why not publish it on https://open-vsx.org for Windsurf and other forks?

For context, Open VSX is run by the Eclipse foundation, which also develops the Eclipse Theia editor, which is basically a clone of VS Code (not a fork, like VS Codium).

The Open VSX registry is open source (https://github.com/eclipse/openvsx) and self-hostable, although I have no experience with that. I assume it's possible to host your own instance with the extensions you want instead of relying on the free public instance.

Personally I'm more of a Sublime guy, but people looking for an open VSC alternative should consider Theia over VSC forks. It seems like the smarter long term investment if you want to get out from Microsoft's control.

I was going to point this weird part of their comment too.

Reminder that the Open-VSX extension registry exists: https://open-vsx.org

Idk if they removed the malicious theme (or if they have it at all), but if MS isn't doing anything beyond just responding to user reports, you might as well switch to an open registry that probably does the same level of security work, and avoid giving them yet another monopoly.

https://open-vsx.org/

We also import your extensions automatically (safe guarding against the ones with Microsoft's licensed)

You can also just download in from the vscode marketplace webpage and drag and drop it in

> Microsoft also made its extension marketplace closed-source so we (and Cursor) have to hack our way through it.

For the marketplace, can you not use Open VSX [https://github.com/eclipse/openvsx]?

I am working on a hobby project in which I need to simulate vim motions outside of vim. I need some API that have functions that would take as input a text, some vim mode and a key (or sequence of keys) and return what is the output text and vim mode. It could be in Rust, C or C++. I tried using libvim (https://github.com/onivim/libvim) but it is way more than I want (and also, I am having a hard time to build it on my machine). Are there any other alternatives?

Hi there! I'm trying to import https://github.com/onivim/libvim in a separate standalone file. But, just cloning the repository and using #include "../libvim/src/libvim.h" doesn't work, as the file contains multiple errors. It seems to me that libvim also have other dependencies that are missing, which causes such errors. If I try to build it, in the way that is explained in README.md it works, but I suppose that this happens because the Makefile adds the necessary dependencies. The Makefile has over 3000 lines, and I don't have much experience on this. Is there a standard way to automatically add any necessary dependencies? Am I using this library in a wrong way?

Oni is a proper neovim gui, whereas Oni2 is something else entirely (uses https://github.com/onivim/libvim).

You might want to look at https://github.com/onivim/libvim Dunno what it's capabilities are, but, it might be of use.

In progress work, but we do use vim under the hood (i.e. a fork of vim, where we've made it more suitable for being used as a library: https://github.com/onivim/libvim). So we can support vim plugins (or at least a subset of them), we just want to have tests back up and running for them in libvim, and have more testing in place at the Oni2 end as well.

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...

FYI, this isn't built on neovim anymore https://github.com/onivim/libvim#why-is-libvim-based-on-vim-and-not-neovim