Disable inbuilt lsp

[Muizzyranking]

I want use the kulala_ls so I want to know if I should disable the one that comes with kulala nvim or I should keep using it.

Is there any advantage to using the standalone lsp against using the one that comes with this plugin?

[YaroSpace]

The built-in LSP is far more advanced than kulala_ls nowadays. The only reason to use it today is when you need its features from outside of Neovim.

[Muizzyranking]

I was thinking of the make capabilities function provided by completion plugins.

Although, I'm already having completions without it but it's somewhat buggy and since I added this capabilities, the experience is better.

[YaroSpace]

Kulala's built-in LSP provides autocompletion. What bugs are you experiencing?

If you want to extend its capabilities, you would have to modify the LSP module source.

Autocommand is only used to start the server, when you enter a relevant buffer.

[Muizzyranking]

Sometimes, it works, sometimes it doesn't. Also, it adds a closing pair but not the opening.

[YaroSpace]

You would need to be more specific for me to fix it.

If by capabilities you meant the lsp capabilities map:

    capabilities = {
      codeActionProvider = true,
      documentSymbolProvider = true,
      hoverProvider = true,
      completionProvider = ....

then no, you do need to specify anything. The built-in lsp does not require any setup.

[Muizzyranking]

Oh. Alright. Thank you very much. I'd let you know if there's more issues in the future.