#languageserverprotocol — Public Fediverse posts

Endlich Phpactor als Language Server mit dem Editor Kate verbunden. Die Einbindung dürfte für meinen Geschmack, wenn man in dem Feld noch nicht so zuhause ist, zwar gerne etwas intuitiver ablaufen, aber ich habe es mir letztendlich mit ein paar thematisch verwandten Dokufetzen zusammengereimt. Mal schauen, als wie hilfreich die Angelegenheit sich erweisen wird, und ob das Einbinden von Servern für HTML, CSS, JavaScript usw. nun anschließend etwas flotter vonstattengehen wird.

#LSP #LanguageServerProtocol #Phpactor

Endlich Phpactor als Language Server mit dem Editor Kate verbunden. Die Einbindung dürfte für meinen Geschmack, wenn man in dem Feld noch nicht so zuhause ist, zwar gerne etwas intuitiver ablaufen, aber ich habe es mir letztendlich mit ein paar thematisch verwandten Dokufetzen zusammengereimt. Mal schauen, als wie hilfreich die Angelegenheit sich erweisen wird, und ob das Einbinden von Servern für HTML, CSS, JavaScript usw. nun anschließend etwas flotter vonstattengehen wird.

#LSP #LanguageServerProtocol #Phpactor

Do you use an LSP for python ? If so, which one ?

I just discovered basedpyright. NUTS. It is hands down the best open source experience I have had developing in this infuriatingly promiscuous language with no concern for runtime safety (I understand the historical reasons... I am just sad it has become the defacto standard for my field).

#python #languageserverProtocol #lsp #emacs #basedPyright

Do you use an LSP for python ? If so, which one ?

I just discovered basedpyright. NUTS. It is hands down the best open source experience I have had developing in this infuriatingly promiscuous language with no concern for runtime safety (I understand the historical reasons... I am just sad it has become the defacto standard for my field).

#python #languageserverProtocol #lsp #emacs #basedPyright

“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).

Via HN: https://news.ycombinator.com/item?id=46719899

On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp

#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing

“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).

Via HN: https://news.ycombinator.com/item?id=46719899

On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp

#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing

Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).

My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.

Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/

Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).

My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.

Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/

@felix
> Out of the box #Emacs lacks modes for a lot of newer languages.

The good news is that #Emacs now has built-in support (via Eglot) for #LanguageServerProtocol, so it can now natively use whatever LSP programs you install.

The bad news is that the LSP ecosystem seems to be really scattered and there's no smooth way to just get general support for arbitrary languages.

So you need to hunt down each one. But it is no longer necessary to get Emacs-specific support.

@felix
> Out of the box #Emacs lacks modes for a lot of newer languages.

The good news is that #Emacs now has built-in support (via Eglot) for #LanguageServerProtocol, so it can now natively use whatever LSP programs you install.

The bad news is that the LSP ecosystem seems to be really scattered and there's no smooth way to just get general support for arbitrary languages.

So you need to hunt down each one. But it is no longer necessary to get Emacs-specific support.

And here it is, the #languageserverProtocol plugin of #suetum for #vscode is mostly done for the features I need right now! Considering this took one and a half day to put together, I'm pretty satisfied with it.

There's tons of improvement that can be done (and I think symbol resolution is something I will sooner or later add), but now I'm up to adding includes (welp, currently the program can only be in a single file!) and debugging tools.

And here it is, the #languageserverProtocol plugin of #suetum for #vscode is mostly done for the features I need right now! Considering this took one and a half day to put together, I'm pretty satisfied with it.

There's tons of improvement that can be done (and I think symbol resolution is something I will sooner or later add), but now I'm up to adding includes (welp, currently the program can only be in a single file!) and debugging tools.

Anyone know of tools kind of like #languageServerProtocol but instead of keeping the AST in memory they do streaming parse / search on the fly? I'm not a huge fan of masssive memory use and it feels like we're leaving performance on the table by parsing entire files/folders instead of just enough to get to what you want.

Anyone know of tools kind of like #languageServerProtocol but instead of keeping the AST in memory they do streaming parse / search on the fly? I'm not a huge fan of masssive memory use and it feels like we're leaving performance on the table by parsing entire files/folders instead of just enough to get to what you want.

I've added the just-lsp package to the set of #ArchLinux packages:
https://archlinux.org/packages/extra/x86_64/just-lsp/

In case you're relying on #just, try it out in with your language-server enabled editor of choice.
It's really quite useful!

#RustLang #LanguageServerProtocol

I've added the just-lsp package to the set of #ArchLinux packages:
https://archlinux.org/packages/extra/x86_64/just-lsp/

In case you're relying on #just, try it out in with your language-server enabled editor of choice.
It's really quite useful!

#RustLang #LanguageServerProtocol

TIL Network protocols Sans I/O ⚡

“… network protocol implementations written in Python that perform no I/O (this means libraries that operate directly on text or bytes; this excludes libraries that just abstract out I/O).” 🤯

Read the reference page 👇
https://sans-io.readthedocs.io/

#Reusability #Python #FastCGI #HTTP2 #H11 #IRC #OAuth2 #OAuthLib #WebSocket #SOCKS5 #RFC2217 #SerialOverIP #EPICS #FIX #QUIC #LanguageServerProtocol #SMTP #DBus #ThorlabsAPT #Matrix #SSL #TLS #CPython #multipart #formdata

TIL Network protocols Sans I/O ⚡

“… network protocol implementations written in Python that perform no I/O (this means libraries that operate directly on text or bytes; this excludes libraries that just abstract out I/O).” 🤯

Read the reference page 👇
https://sans-io.readthedocs.io/

#Reusability #Python #FastCGI #HTTP2 #H11 #IRC #OAuth2 #OAuthLib #WebSocket #SOCKS5 #RFC2217 #SerialOverIP #EPICS #FIX #QUIC #LanguageServerProtocol #SMTP #DBus #ThorlabsAPT #Matrix #SSL #TLS #CPython #multipart #formdata

@b0rk thanks for sharing this. I’d already had a play with the #HelixEditor (impressive first class #LanguageServerProtocol support) and had a look tonight at the #MicroEditor (nice mouse support, assorted plugins but no official channel). Neither seems a perfect match but with a little personalisation either might serve - precisely your wider point about effort and configuration 😉

@b0rk thanks for sharing this. I’d already had a play with the #HelixEditor (impressive first class #LanguageServerProtocol support) and had a look tonight at the #MicroEditor (nice mouse support, assorted plugins but no official channel). Neither seems a perfect match but with a little personalisation either might serve - precisely your wider point about effort and configuration 😉

Because I too want to post a nice screen shots of Emacs once in a while.

Implemented https://codeberg.org/harald/eglot-supplements/issues/23 for my eglot-supplements: https://codeberg.org/harald/eglot-supplements

#emacs #eglot #eglot-supplements #lsp #languageserverprotocol

If you are using Emacs with Eglot and a language server, you may be interested in eglot-cthier.el (formally eglot-hierarchy.el) which alles to show and navigate the call hierarchy of an item.

After feedback here, on the mailing list and on codeberg, an improved version is ready for testing.

I tested it with eclipse-jdtls and tsc.

Feedback welcome.

#Emacs #Eglot #LSP #language_server #LanguageServerProtocol #eclipsejdtls #tsc #Typescript
#codeberg

https://codeberg.org/harald/eglot-supplements#call-hierarchy

If you are using Emacs with Eglot and a language server, you may be interested in my new package eglot-hierarchy.el which alles to show and navigate the call hierarchy of an item.

I tested it with eclipse-jdtls and tsc.

Feedback welcome.

#Emacs #Eglot #LSP #language_server #LanguageServerProtocol #eclipsejdtls #tsc #Typescript

https://codeberg.org/harald/eglot-supplements#call-hierarchy

And now there's also a watch system integrated. I think it's now ready enough to test in our next project and then release it for the public.

#ink #vscode #lsp #languageServerProtocol #language_server_protocol

And now there's also a watch system integrated. I think it's now ready enough to test in our next project and then release it for the public.

#ink #vscode #lsp #languageServerProtocol #language_server_protocol

#Nushell and #HelixEditor connected via #LanguageServerProtocol a.k.a. #LSP

My pull request got merged, now you get diagnostics with each keystroke.

Finally, I got this PR into a state where I think it can be merged. https://github.com/nushell/nushell/pull/10723#issuecomment-1789666065

Let's see if the #maintainer|s accept it as is and if #nushell get initial #LanguageServerProtocol support with the next release.

Let's see if my attempt of integrating the #LanguageServerProtocol a.k.a. #LSP into #Nushell will be successful.

https://github.com/nushell/nushell/pull/10723

I've been implementing the #LanguageServerProtocol ( #LSP ) for #nushell , which is mostly me taking some existing TypeScript and rewriting it in #Rust , but with some server process and multi-threaded stuff thrown in: https://github.com/jokeyrhyme/nuls

It's already working well enough to be useful, and hopefully it won't be long before it reaches parity with the existing extension for Visual Studio Code

If you're already a nushell ( http://www.nushell.sh/ ) user and don't use Visual Studio Code, then maybe give this a try and let me know how it goes!

Alright, there’s actually another widely-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

Check out Jessica's blog post about the latest release of VS Code #Quarkus: https://quarkus.io/blog/vscode-quarkus-1.13.0-released/ . She does a great job of giving in depth explanations about the new features we've added.

#VSCode #Qute #LanguageServerProtocol

Just released lemminx 0.25.0! This release focuses on bug fixes, including preventing a few NullPointerExceptions and fixing a protocol violation that was causing issues in #helix .

See the changelog for more info: https://github.com/eclipse/lemminx/blob/main/CHANGELOG.md#0250-april-18-2023

#xml #LanguageServer #LanguageServerProtocol

Are any #swift developers interested in working on trying to get SourceKit-LSP to work with #Xcode projects? With the upcoming demise of #AppCode, I’m looking for alternatives, and a solution that involves #SourceKit, #LSP, and can understand Xcode projects seems the most promising as it can be used in any editor with #LanguageServerProtocol support.

https://github.com/apple/sourcekit-lsp

Are any #swift developers interested in working on trying to get SourceKit-LSP to work with #Xcode projects? With the upcoming demise of #AppCode, I’m looking for alternatives, and a solution that involves #SourceKit, #LSP, and can understand Xcode projects seems the most promising as it can be used in any editor with #LanguageServerProtocol support.

https://github.com/apple/sourcekit-lsp

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

Yeeaaaaah \o/.

#helix #editor #lsp #LanguageServerProtocol

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

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.

The demise of #AppCode is just so depressing. Despite its warts there was nothing better for raw code editing and refactoring. Every time I open it it makes me sad. I thought I would have a good amount of time before being forced to stop using it, but the latest release is just so unstable — crashing multiple times a day. Switching back to Xcode feels like coding with my hands tied behind my back. I’ve started looking into #Swift #LanguageServerProtocol in either #vim or #emacs. <sigh>

#Introduction
Hi! I'm David/Dave (any pronouns), and I'm a #DevTools developer at IBM (and previously at Red Hat). I work on #VSCode extensions, such as #XML, #YAML, and #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, #TTRPG #VirtualReality, #EDM, and #Camping