Skip to content

Conversation

@matmatias
Copy link

About

Add mason_lspconfig default_handlers instead of traditional nvim-lspconfig setup for each language.

Benefits

This will make you have a default handler when you install a new language server, making it unecessary to setup a new nvim-lspconfig for each new language server that don't require a custom setup. You can still customize new language servers setup, passing a function to it's name's property in the setup_handlers argument table.

Fix an error that was being caused because setup_handlers was being called from nvim-lspconfig instead of mason-lspconfig
@matmatias
Copy link
Author

#44

Copy link

@MuhammadcodR MuhammadcodR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I check your modification that's GOOD!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants