libvim VS nvim-treesitter

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

I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.

These two plugins are the bare minimum in my view.

https://github.com/nvim-treesitter/nvim-treesitter

Treesitter gives you much better syntax highlighting based on a parser for a given language.

https://github.com/neovim/nvim-lspconfig

This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:

https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...

For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.

pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server

Best of luck! Happy hacking.

It was changed in https://github.com/nvim-treesitter/nvim-treesitter/commit/78b54eb

https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.

vim.opt.rtp:prepend(lazypath) require('lazy').setup({ { "nvim-neorg/neorg", build = ":Neorg sync-parsers", opts = { load = { ["core.defaults"] = {}, -- Loads default behaviour ["core.concealer"] = {}, -- Adds pretty icons to your documents ["core.dirman"] = { -- Manages Neorg workspaces config = { workspaces = { notes = "~/notes", }, defaultworkspace = "notes", }, }, }, }, dependencies = { { "nvim-lua/plenary.nvim", }, { -- YOU ALMOST CERTAINLY WANT A MORE ROBUST nvim-treesitter SETUP -- see https://github.com/nvim-treesitter/nvim-treesitter "nvim-treesitter/nvim-treesitter", opts = { auto_install = true, highlight = { enable = true, additional_vim_regex_highlighting = false, }, }, config = function(,opts) require('nvim-treesitter.configs').setup(opts) end }, { "folke/tokyonight.nvim", config=function(,) vim.cmd.colorscheme "tokyonight-storm" end,}, }, }, }) require 'plugins' ```

Change the compiler to use 'llvm' and install visual studio build tools command line stuff - at least that is what worked for me without problems. If you are using c++ then I would assume you have visual studio installed already. If you need more info follow the treesitter windows support

After a lot of time spent yesterday I took a fresh look today and then thought to myself - what if this is what TS does by design? A few clicks later and I found this https://github.com/nvim-treesitter/nvim-treesitter/issues/1327

I've followed the official guide for nvim-treesitter support on Windows, but I'm having problems making it work. I keep getting a compilation error for any parser I try to install using TSInstall. If instead I use TSInstallSync I don't get errors but the parser is not correctly installed. My setup uses lazyvim and I installed LLVM using winget to have a C compiler.

I have read that gcc in windows doesn't always provide the necessary support for treesitter. I have seen ppl prefer clang over gcc in Windows. Please see also Windows support in treesitter's repo. Unfortunately I cannot help further as I don't use Windows for coding, but hope you can deduce something to solve your problem from the above link (if you haven't already read through it).