cmake4vim VS mason.nvim

The plugin is here and adds features like kits, customizable build types, support for running ctest, automatic updates/restarts of clangd LSP server and also provides some functions that allow cool plugin customization. Basically, you get features that are mostly equivalent with features from the plugin I used in vim, but implemented in Lua. Feel free to test it out. Note that I only tested it on my machine (M1Pro mac) and in one Linux container, so expect bugs, crashes and various errors. Feel free to post issues and PRs with fixes.

The plugin depends on cmake4vim (a plugin for CMake integration with Vim/Neovim), this allowed to have deeper integration of gtest-vim for CMake projects (you can just switch between CMake targets in order to run different tests).

Around the year ago, I have posted the last post about cmake4vim plugin updates.

CMake integration: https://github.com/ilyachur/cmake4vim

Not sure if you want to add a other plugin, but I've had good results with cmake4vim. It integrates with Dispatch if it's installed.

Good question! And for Cmake projects I really like the cmake4vim plugin from ilyachur. https://github.com/ilyachur/cmake4vim

I think, that you can do such 'advanced' features without used plugins. Concerning my C++ workflow, I'm using it with Cmake and https://github.com/ilyachur/cmake4vim plugin adds the possibility to compile it in a few commands. Also, I've added a feature to run the CMake target with the use of one command and hope, that soon it will be merged.

Here is the issue with the video https://github.com/ilyachur/cmake4vim/issues/68

I recently started coding with Neovim using kickstart.nvim as the template for my editor configuration. I downloaded the python-lsp-server package using Mason, but I was disappointed to discover that the IntelliSense on my third party dependencies didn't work. The LSP was resolving to my global Python installation, which did not have the packages from my virtual environment (venv) installed.

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.

I'm using mason.nvim to install my dependencies, I've this snippet at nvim/plugin/mason.lua so after cloning my dotfiles I can just run:

The suggestion from this thread fixed it for me. I just needed to unset GOOS and GOARCH then restart neovim.

For instance, I'm trying to install rust-analyzer in lazyvim from https://github.com/williamboman/mason.nvim. The installation instructions are:

I have pyright installed via mason which apparently support "semantic token highlighting" but have been having a hard time getting these colors to show up in a buffer. It seems Neovim has changed how it handles semantic highlighting a few times so there's still some conflicting information online. It's hard to know what's current and what's not. Any help would be greatly appreciated.

Use mason to install the language servers you want.

Because null-ls.nvim & mason.nvim together do everything I wanted CoC for