New: Julia for JetBrains IDEs (Flexible Julia)

Tooling
61

New Release: Flexible Julia 2026.2.0

Let’s keep the energy going in 2026. So here’s the new release that was just approved on the marketplace:

New Features:

  • Dot-Method Completion: GoLand-style method discovery - type obj. to find methods like filter(obj, ...)
  • Go to Implementation: Ctrl+Alt+B now works for Julia multiple dispatch methods
  • LSP Status Indicator: Now shows degraded status when the language server is responding slowly

Fixes:

  • IDE freeze when switching between LanguageServer.jl and JETLS
  • Duplicate plots appearing in gallery
  • Clear button not fully clearing plots (old ones would sneak back)
  • Cross-file navigation failing when target file wasn’t open
  • LSP status bar showing “Ready” while server was actually unresponsive
  • Member access navigation (obj.method clicks now properly navigate to method)

So, I focused on seemingly minor issues for this, that required a few more detailed grammar improvements (those are always kinda nasty to fix). The dot-method completion is a big one - typing obj. now discovers all methods that accept that object as first argument, similar to how GoLand handles it. Combined with Go to Implementation support for multiple dispatch, navigating Julia codebases should feel a lot more natural.

Also squashed a bunch of annoying bugs - the IDE freeze when switching language servers was particularly nasty.

I am slowly working on improving the internal reference annotator, so that someday the plugin could work faster without need for the addition of a language server. However, for now it is still smart to just enable it and have it run with merged responses.

Up on my list for the near future: I really found the complaints in the other chat intriguing, so I will spend some time on thinking about ways to improve the experience for all. (Reflections on Developer Experience After Building a Large Julia Codebase - #22 by cuihantao). To me some of these issues derive from how tools were built in the past - all driven by the Julia language perspective and more as peripherals, rather than their own things. So maybe my fresh perspective can make a difference here.

Apart from that: i still want to find ways to improve startup time and indexing time of the Language Server, so I will take another look at the vscode plugin and see if they do something different from what I am doing here.

@PetrKryslUCSD: Thank you for the detailed bug reports - really helped track these down!!!
@csvance: Thanks again for your feedback - all addressed in this release :slight_smile: .

13 Likes