dotfiles VS mason-lspconfig.nvim

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

I use neovim for typescript development on a daily basis. Feel absolutely free to browse through my config

Feel free to browse through my config and take what you want from it, it’s beginner friendly and specifically targeted for frontend development

I got this same stuff at one point (tho with copilot.vim) and it was because I had a duplicated map on , maybe it’s something related? Here my config in case you need it

Anyway, here’s my dotfiles in case it helps https://github.com/gonstoll/dotfiles. It’s from a beginner so I think not much complexity is there. I’d be happy to help if you have any doubts!

Find my `nvim` config here.

How do you find the configuration for your language? This package manager has a List with all supported language servers, look for the language you need there, in nvim through the command :Mason look for the package name as in the table, and install, then in the next column open the link to the language server, and take the configuration from there. Let's install the language server for all languages that i use as an example

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.