Language server doesn't start

[Jollywatt]

With the julia binary pointing to this version:

julia> versioninfo()
Julia Version 1.12.6
Commit 15346901f00 (2026-04-09 19:20 UTC)
Build Info:
  Official https://julialang.org release
Platform Info:
  OS: macOS (arm64-apple-darwin24.0.0)
  CPU: 8 × Apple M2
  WORD_SIZE: 64
  LLVM: libLLVM-18.1.7 (ORCJIT, apple-m2)
  GC: Built with stock GC
Threads: 1 default, 1 interactive, 1 GC (on 4 virtual cores)

Please forgive the screenshot - the "Click to show error" button does nothing and the LSP logs are all empty.

Zed 1.1.7
Commit: c17f25cd782edffab64b7c4167abfa44f865b125
Version: 1.1.7+stable.268.c17f25cd782edffab64b7c4167abfa44f865b125

[piechologist]

Weird, looks like julia wants to run an interactive REPL...

The extension basically runs julia --project=@zed-julia --startup-file=no -e 'using LanguageServer; runserver()'. Does this work in Zed's terminal?

If there is a problem with the language server, have a look at #50.

[Jollywatt]

The extension basically runs julia --project=@zed-julia --startup-file=no -e 'using LanguageServer; runserver()'. Does this work in Zed's terminal?

I'm not sure what "work" means here, but running this in Zed's terminal doesn't crash with the same error as emitted in the logs for me. It just spends a while caching every package in my base environment (I hope that doesn't happen when I use the language server in a project…) and then finishes with

[ Info: Loaded all packages into cache in 4.8s

and hangs.

[piechologist]

At least, the LS launches. It's then waiting for input which looks like hanging.

When I open a .jl file in a project, then open Zed's Command Palette and search for zed: open log the logs shows:

2026-05-15T21:47:35+02:00 INFO  [lsp] starting language server process. binary path: "/Users/me/.juliaup/bin/Julia ...many arguments"

It just spends a while caching every package in my base environment (I hope that doesn't happen when I use the language server in a project…)

I'm afraid you'll be disappointed. LanguageServer.jl is not exactly fast. It can turn the Zed experience into a VS Code experience, particularly on an older machine.