vim-helm VS mason-lspconfig.nvim

I use vim-helm plugin that detects "helm" filetype and sets it for some yaml files. I also have both yaml and helm language servers installed (via mason-lspconfig). The problem is, when opening .yaml file that is actually a helm file, I get both yaml and helm language servers being attached to this buffer, while I actually want only helm one. Is there a way I can prevent that from happening?

https://github.com/towolf/vim-helm Not tressitter, but works ok for highlighting

This https://github.com/towolf/vim-helm ?

I noticed this with xit.nvim and vim-helm. No idea why, but it seems that plugins that provide custom highlighting just don't work for me!

You can use https://github.com/towolf/vim-helm and something like that in your lsp config:

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.

pylsp offers an option to install flake8 as an optional plugin and Mason offers a command to install pylsp plugins. I could then install flake8-pytest-style via pip. Then pylsp and flake8 would live in the same Mason environment and flake8-pytest-style would live in my project's environment. I don't know if/how they will communicate with each other.

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

Have you set up https://github.com/williamboman/mason-lspconfig.nvim as well?

You can also use https://github.com/williamboman/mason-lspconfig.nvim with nvim-lspconfig to make language server installation closer to installing a vscode extension, in that you just install a language server through mason and it'll be automatically configured for you.

https://github.com/williamboman/mason-lspconfig.nvim - Mason plugin to manage your LSP servers.

I found this GitHub issue: https://github.com/williamboman/mason-lspconfig.nvim/issues/224 I think it could be related, but I'm not sure.

LSP: lspconfig & mason-lspconfig.nvim"