A new release of the Open Dylan compiler, IDE, and tools is now available for download! It has been a while since we've done a release and this release includes various bug fixes for the compiler, a new multi-line string literal syntax, the Dylan LSP server for emacs and VS Code, and enhancements to Deft, the Open Dylan command-line tool.

See the 2025.1 Release Notes for an overview of what's in this release: https://opendylan.org/release-notes/2025.1.html

https://opendylan.org

I was just wondering if I am the only person among the FreeBSD users having issues with LSPs? Seems like there are many LSPs that are not working under FreeBSD. Tried to integrate some in my Neovim setup just to notice that quite a lot of them are not working or at least are not supported on FreeBSD Mason and Lazy seem to complain about everything. How are you guys dealing with this?

Trying out #astral #ty as my #python #lsp in my #neovim configuration.

So far so good! And it does seem a lot faster than pyright or basedpyright.

#emacs folks who program #java show me your config files!

I'm looking for moving from intelij to emacs if possible. #lsp-java seems good... is that what you use? I'd love to have it connect up to my ollama server for code completion too.

I'd like to break the intelij cycle and get back to Emacs for everything. Any advice I'll take

@stib Shouldn't it just work out of the box if your #LSP supports the `textDocument/documentColor` method as mention in the PR? I'm using #tailwindcss-language-server for #CSS and it does show the swatches in the completion picker w/out any extra config.

There's a dedicated LSP mentioned in the PR that displays the swatches right in the document buffer as well: https://github.com/q60/uwu_colors (haven't tried it).

PR: https://github.com/helix-editor/helix/pull/12308

LEGO® SERIOUS PLAY® Methode, und um alle zu ermutigen, sich an der Lösung zu beteiligen, einen Beitrag zu leisten und sich dafür zu engagieren

So wie die LEGO Gruppe seit Jahrzehnten Kinder dazu inspiriert, ihre Träume zu verwirklichen, können Erwachsene auch mit #LegoSeriousPlay ihre Visionen für zukünftige Strategien entwickeln.

Im Jahr 2010 beschloss die #LEGO Gruppe, die #LSP-Methode als Community-basiertes Modell unter der Creative Commons-Lizenz anzubieten.

https://www.lego.com/de-de/themes/serious-play/background

A lot of trouble with the new #Vue #LSP.

First, it disables all other typescript LSPs, even if there is no Vue in the project; fortunately, this can be fixed with:

(setq lsp-volar-take-over-mode nil)

Maybe a better way would be to advise `lsp-volar--activate-p' to detect Vue by parsing package.json.

Second, somehow the server sends empty "textDocument/publishDiagnostics" messages about a second after sending one with diagnostics! As a result, the diagnostics appear for a second and then disappear.

For now, I've worked around that by advising `lsp--on-diagnostics' to ignore empty messages if they come less than five seconds after a non-empty one. Not sure where to go next with this.

The code: https://sqrtminusone.xyz/configs/emacs/#fix-vue-semantic-server

Finally, the server sometimes crashes randomly. It happened once or twice today.

Hit an interesting limit in the TypeScript language server¹:

Looks like there’s a limit on the number of entries an object (constant) can have before the language server balks. Seems to hit it around 1,343.

(I’m generating an object for an icon library.)

Doesn’t appear to be related to file/memory size (breaking up the same number of entries into several objects works).

Anyone know what limitation exactly I’m hitting (if it’s documented somewhere?) Been searching but couldn’t find any reference to it.

¹ It’s definitely a language server limit as I tried in VSCode as well to rule out it being a limit in Helix Editor.

Nice LSP feature I just learned about from Eric Dallo:

lsp-signature-activate (in emacs lsp-mode), it shows the arg names and docstrings of a function you're currently calling inline

I am amazed, #neovim with #clang #lsp is GREAT, I just learned how to enable inlay hints and found a nice signature help plugin. A big THANK YOU to everyone making this possible. #llvm

#MasterMe von @trummerschlunk@chaos.social @falktx@mastodon.falktx.com benutze ich seit es das gibt für meine Projekte fast immer. Vielen Dank für dieses #OpenSource Tool!
Manchmal ist aber hinten dran das #LSP #Clipper noch nötig. Besonders wenn es um Onlineaufnahmen mit suboptimalem Audiokonferenzequipment geht.
So auch bei der Vorbereitung dieser Tagung zur #Inklusion:
https://bildung.social/@komin/113803547189314869

#Audio #FX

My experience with Pylsp-tramp

#emacs #justEmacsThings #JustGirlyThings #LSP #Python

I would like to give back to 2 projects that gave me a lot, #Emacs and #fsharp.

Since it seems there is not a comprehensive Tree-sitter mode for F# yet, I gave myself the (long term) challenge to learn enough about #Tree-sitter, major modes, #LSP and the like to write one (or at least to contribute to one).

Along the way, I promised myself to share in blog posts what I happen to learn.

Here's a first article with the notes taken while wrapping my head around Imenu.

https://arialdomartini.github.io/emacs-imenu

I'm really happy to present, with @tarides #OCaml Eglot, an #Emacs (minor) mode for editing OCaml code, using LSP through Eglot, the built-in #LSP client of Emacs: https://github.com/tarides/ocaml-eglot

Feedback, contribution and RT much appreciated

I did it again: a new supplement for Emacs' Eglot package: eglot-selran gives you access to the language server's textDocument/selectionRange API.

Read more: https://codeberg.org/harald/eglot-supplements#selection-ranges

Feedback welcome.

#eglot #emacs #eglot-supplements #lsp #languageserver #codeberg