friendly-snippets VS language-server-protocol

Those definitely seem to be coming from friendly-snippets, so it seems like it's not being disabled. You can verify this with the :Lazy command to bring up the lazy.nvim menu then checking log or debug to see what is loaded, when, and why.

Here you go :), tested with friendly-snippets lazy loaded (Non lazy-loaded is 500ms)

Snippets for code comments.

I am trying to add snippets for python, i have LuaSnip and friendly-snippets installed, but for some reason it does not load the snippets. This is how i load the plugins:

I just sent [this PR](https://github.com/rafamadriz/friendly-snippets/pull/301) that implements the [full TSdoc specification](https://typedoc.org/guides/overview/) in [friently-snippets](https://github.com/rafamadriz/friendly-snippets). In practice what you get is autocompletion in your typescript comments, which should be a nice of life improvement for most typescript developers.

You mean snippets? If yes, you can try Luasnip and friendly-snippets with nvim-cmp and here's the setup guide. Hope it helps

For example Luasnip with (I guess) friendly-snippets has multi line snippets defined by default. And you can use luasnip with nvim-cmp (read the docs or I guess there’s a YouTube tutorial)

If you copied the config in the readme, then the snippet come from friendly-snippets.

I would recommend lsp-zero, the tsserver lsp provides code actions for auto import. There is auto import when confirming completion as well, I've seen it working with cmp, however I can't remember If that is out of the box behaviour. For snippets, I would go with LuaSnip - It's very versatile snippet engine and it integrates well with many snippet formats. There are specifically react es7 snippet definitions in the friendly-snippets repo which can be used by LuaSnip - https://github.com/rafamadriz/friendly-snippets/blob/main/snippets/javascript/react-es7.json

I've implemented a LSP server (for Slint - https://slint.dev) and I agree with this article.

The paradox is that it was meant to avoid to write language support for each editor. Yet, if you want to support vscode you must create a specific extension for it and can't just have a language client.

The article mention the configuration problem, but I'd add the problem that Microsoft refuses to specify a way for the server to tell the client what are the config options so that the client can show some kind UI showing the possible configuration options with a description of what they do. https://github.com/microsoft/language-server-protocol/issues...

Which is an implementation of Language Server Protocol for Rust programming language. It provide a lot of useful features for your development in Rust, such as code completion, syntax highlighting, inlay hints, etc. You can checkout the manual of rust analyzer to know more about it.

From the LSP website:

But these are typically filling the usecases of productivity applications, not ‘engines’.

Microsoft Word doesn’t run its grammar checker as an external service and shunt JSON over a localhost socket to get spelling and style suggestions.

Photoshop doesn’t install a background service to host filters.

The closest pattern I can think of is the ‘language servers’ model used by IDEs to handle autosuggest - see https://microsoft.github.io/language-server-protocol/ - but the point of that is to enable many to many interop - multiple languages supporting multiple IDEs. Is that the expected usecase for local language assistants and image generators?

If you tried writing code like the one above, your Rust LSP should already be telling you that what you're doing is unacceptable:

A language server is an external program that follows the Language Server Protocol. The LSP specification defines what type of messages a language server can receive, and also how it should respond. The idea here is that any tool that follows the LSP specification can communicate with a language server.

> There's a strange dance of IDEs coming and going, with their idiosyncracies and partial plugins.

The Language Server Protocol [1] is the best thing to happen to text editors. Any editor that speaks it gets IDE features. Now if only they'd adopt the Debug Adapter Protocol [2]...

[1] https://microsoft.github.io/language-server-protocol/

[2] https://microsoft.github.io/debug-adapter-protocol/

The Gno Language Server (gnols) is an implementation of the Language Server Protocol (LSP) for the Gno programming language. It is similar to the equivalent “gopls” project for Go, as they can be plugged into your code editor through extensions and allow you to access handy features, such as autocompletion, formatting, and compile-time warnings/errors. Gnols makes writing code simpler, working with several editors to suit your preferences. To try it out, visit the CONTRIBUTING.md file, which contains instructions to get you started. Our current documentation targets Vim, Neovim, and SublimeText, but can likely be used with any editor that supports LSP. Feel free to contribute to improving Gnols and adding more features. It’s well-written, and simple to dive into the code and add more capabilities.