Skip to content

Use Case: default or lsp-auto-setup.nvim #4

@barrett-ruth

Description

@barrett-ruth

Hi, I have a quick guess about the use case of this plugin. I'll just contextualize this with the experience I'm looking for:

  1. Define an lsp config in lsp/
  2. That configuration is merged with nvim-lspconfig's default configuration
  3. Also be able to easily apply my own on_attach logic, which I now realized is possible with lspconfig.util.default_config

Currently, lsp-auto-setup.nvim lets me do all this with ease. My one gripe: I don't automatically want every single LSP under the sun to be automatically picked up. I suppose I'm suggesting the following option include:

{
   ...
  opts = {
    -- List of server names to include with auto-setup - mutually exclusive with exclude
    include = {},

    -- List of server names to exclude from auto-setup
    exclude = {}
    }
  }
}

I ask for this feature because I'm getting random diagnostic errors for digestif, ttf-vmi-blah blah, and a bunch of LSPs with binaries indeed on my PATH that still end up breaking and bombarding my editor with errors. Each time I have to manually add the LSP list to be excluded in the configuration

What do you think?

||Personally, I think both my request and parts of lsp-auto-setup.nvimwill eventually be baked into neovim core.||

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions