Alright, there’s actually another wildly-used implementation of LSP for Python called python-lsp-server, and it doesn’t need all the node.js nonsense.

Just did a pip install via the corporate pypi mirror, and et voilà! I have LSP support now.

#Python #LanguageServerProtocol #offline

https://fosstodon.org/@kotatsuyaki/110701417022930605

LSP type hints in Helix, https://github.com/helix-editor/helix/pull/5934.

Yeeaaaaah \o/.

#helix #editor #lsp #LanguageServerProtocol

clangd, https://clangd.llvm.org/.

clangd is a language server for clang C++.

#cpp #clang #LanguageServerProtocol

ccls, https://github.com/MaskRay/ccls.

C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting.

#c #cpp #lsp #LanguageServerProtocol

@jntrnr, I was diligent and created https://github.com/nushell/nushell/issues/7982 and https://github.com/nushell/nushell/issues/7983 to report these completion issues.

Thanks for pointing out that there is a treesitter module. I'll try it and it seems active. Do you plan to support treesitter in the future. I'm also wondering if there is #LanguageServerProtocol support on the road map.

It is unfortunate that #elpy is unmaintained.

The closest match to elpy using the #LanguageServerProtocol was initially written by Palantir which makes me feel dirty. But so does all the warnings generated by loading elpy into #emacs 28.

https://github.com/python-lsp/python-lsp-server/blob/develop/LICENSE#L3

@sandipb @anildash Yeah? Ever try finding editor extensions or #LanguageServerProtocol ( #LSP, another #Microsott invention ) going on any other editor? It’s #VScode first and then scraps for anything else.

Finally, I've got #Sonarlint running in @neovim through #languageserverprotocol with #stdio channel.

https://github.com/SonarSource/sonarlint-language-server/pull/187

#neovim

#Introduction
Hi! I'm David/Dave (he/him/his), and I'm a #DevTools developer at Red Hat. I work on #VSCode extensions, such as #XML, #Quarkus, #MicroProfile, and recently #Java. This also involves working on #Eclipse, since vscode-java is based on Eclipse's Java features (JDT). The core features of these plugins can be reused in other editors (such as Eclipse and #neovim ) since they use the #LanguageServerProtocol.
Outside of work, I enjoy #RockClimbing, #VirtualReality, #EDM, and #Camping.

I created a PR that supports the generation of JSON compilation database in #Rust projects that use the #C++ brideging. Have a look:

https://github.com/rust-lang/cc-rs/pull/682

Now it is poosible for me to work on a #Rust project that embeds @libreoffice C++ API with my #Neovim setup through the #LanguageServerProtocol

In my journey to #neovim I had some joy to extend #eclipse's #languageserver. It is now more convenient to start (wrapper start script, https://github.com/eclipse/eclipse.jdt.ls/commit/7a5ba470 ) and now I want it to emit some standard #languageserverprotocol event: https://github.com/eclipse/eclipse.jdt.ls/pull/2030

With this fix my #neovim setup will print some nice progress information through https://github.com/j-hui/fidget.nvim

@schmittlauch Here it is: https://code.sourcephile.fr/julm/home-julm.git/blob/HEAD:/.config/nixpkgs/home/vim/ale.vim
Note that last time I checked the IsCheckingBuffer part to print "..." in the status bar, will not work when using the #LanguageServerProtocol like #hie does. I've tried to fix this in #ALE with https://github.com/dense-analysis/ale/pull/3076 but my PR got completely ignored. Also, my completion setup is still in progress: I've set C-p to use semantic and kept C-n for syntaxic. In the same directory you'll find old confs for #LanguageClient and #CoC.