Pluto.jl Support: .jl files starting with ### A Pluto.jl notebook ### now open directly in the notebook editor
Interactive Widgets: Pluto cells support @bind widgets - Slider, Scrubbable, NumberField, CheckBox, TextField, Select - with automatic downstream cell re-execution on change
New Pluto Files: Create Pluto notebooks via File → Julia → Pluto
Fixes:
REPL-based inline rendering of cell output for Jupyter and Pluto
Pluto notebook support is here!!!
Pluto.jl notebooks now work natively in the IDE. Drop a .jl file that starts with the Pluto header and it opens right in the notebook editor - no separate Pluto server needed. The reactive @bind widgets work too: move a slider, and downstream cells automatically re-run. I tried to mimic a bit of what the awesome team of pluto.jl is doing (https://plutojl.org/). And though theirs is more complete, this is a step into their direction. Call it a love letter, really, because I think they are on the right track with what they are doing (and if you haven’t check out their project and give them a star on Github!)
I also used this opportunity to fix inline rendering for regular jupyter cells. That was broken because of a race condition… anyway, have fun
As nobody reported any bugs this week or feature requests, I decided on just doing a quality-of-life one.
I added “safe delete” - one of those refactoring features you don’t know you need until you have it - finds all usages before removing a function/type/module/macro and warns you if something would break.
Also improved LaTeX symbol completion.
Speaking of auto completion, I also tweaked completion ranking so the methods you actually use (push!, pop!, etc.) show up higher and I made sure that auto completion now triggers if enabled in your settings.
Julia Spellcheck Dictionary: Bundled dictionary with Julia keywords, stdlib modules, and common package names - no more red squiggles on DataFrame or AbstractArray
Find Usages Improvements: Better grouping, highlighting, and overall presentation
Extend Word Selection: Ctrl+W now smartly expands through bracket content, block bodies, and if-clause ranges
Another quality-of-life release building on 2026.9.33.
The spellcheck dictionary is a nice follow-up - I noticed that julia specific terms were sometimes highlighted in our spellchecker, so I now added some fix for that.
Extend Word Selection (Ctrl+W) is now a bit improved, too Selection now expands intelligently through brackets, blocks, and if-clauses instead of grabbing random chunks.
And I also worked a bit on the “Find Usage” (Right click - find usage) logic. It now groups nicely, auto-highlights , etc etc
Less people posting now because we are enjoying being productive with Flexible Julia!
I do have one question, is there a way to set the default language server? I’d always like to default to JETLS. When I open a project the IDE often gets into a doom loop trying to restart the default language server.
Yes essentially it would be nice to have a configurable default. Recently I have been doing alot of up-streaming changes to many different repos needed for a project I’m working on. That means that every time I clone my fork first thing I need to do is go into Settings → Language → Julia → LSP and set it to JETLS. I don’t have LanguageServer installed, so it tends to restart several times and cause hangs / performance drops.
Global Default Settings: Configure defaults for LSP, editor, formatter, debugger, and REPL at Settings - Languages & Frameworks - Julia - Defaults - new projects inherit these values automatically, project-specific settings override them (#125)
Here it is: You can now set your preferred Julia configuration once and have it apply to all new projects automatically. LSP settings, editor preferences, formatter options, debugger behavior, REPL configuration - set it and forget it.
Project-specific settings still override the defaults when you need them to.
One more feature request: Add an assistant for creating a Julia project. It could come in three flavors:
Create a Julia project that is NOT a Julia package
Convert an existing Julia project to a proper Julia package
Create a new Julia project that is a proper Julia package
Both could be implemented by a set of dialogs.
I know, there is PkgTemplates.jl, BestieTemplates.jl, and other packages for this purpose. But I don’t think they are easy to use for beginners. Such an assistant should also guide you in creating a GitHub project. The GitHub project should have the suffix .jl, the local project not.
BestieTemplates has the disadvantage of relying on Python. And PkgTemplates is somewhat outdated.
Features I would like to see:
Beginners mode
Advanced mode
Dialog to enter package name, author name, eMail, License, GitHub URL, local folder
Dialog to choose if you want to use sub-projects; if yes, which sub-projects (like test, docs, examples, etc); if no, which sub-folders to add (without adding a Project.toml to the sub-folders)
Option to put the test dependencies in the main Project.toml or in a test/Project.toml
Options to add .JETLSConfig.toml, README.md
Option to add Documenter
Option to create a CI workflow
Option to add one or more of the common plotting packages (like Plots, PythonPlot, ControlPlots, MakieControlPlots, GLMakie etc) to the examples sub-project
Option to add a script that runs Julia to the bin folder
Option to add an install script to the bin folder
Option to add an create_sys_image script to the bin folder
Option to add a basic example to the examples folder
And more…
Digression:
When is a script to run Julia useful?
It can be used to:
set environmental variables
detect and use the right system image if available
load Revise
load Kaimon.jl, if the Kaimon server is running
Goal:
Make it easier for students and researchers to get started with professional Julia package development.
Simple question : what is the best (recommended) way of using Pycharm/FlexibleJulia from inside WSL ?
eg, as I have already install Pycharm in Windows, should I install the Linux version in WSL?. Or is there a canonical way to launch the Windows version, as for VsCode?
The simplest setup is to run Julia natively on Windows. Install it with juliaup or the official installer, PyCharm will detect it automatically, and everything works out of the box.
If you need Julia inside WSL, native WSL support isn’t available yet (I just didn’t think of it yet), but I will push an update later and include it there. In the meantime, you can use the Remote REPL feature (Settings - Julia - REPL) and connect to a Julia session running in WSL over SSH.
A simple setup is:
sudo apt install tmux openssh-server
tmux new -s julia
julia
Detach with Ctrl-B D and the session will keep running. Start SSH with:
sudo service ssh start
Then connect to WSL via SSH and point the Remote REPL at that host. (I did a similar thing here, albeit with a docker container, to test tmux support)
I’m currently adding proper WSL SDK support so you’ll be able to use a Julia installation inside WSL directly from PyCharm.
No need to install a Linux IDE - your existing Windows PyCharm is fine.
This is awesome! For quick workflows I find myself often getting out of sync between my terminal and my PyCharm/Flexible Julia sessions. Having the ability to do this with the UI reduces friction.
Julia Package Creation Wizard: Multi-step guided package scaffolding via File - New Project - Julia with preset cards (Basic, Documented, Full, Custom), sub-projects (test/docs/examples), license selection, README, Documenter.jl, GitHub Actions CI, plotting packages, and utility scripts
WSL Support: Detect and use Julia installations inside Windows Subsystem for Linux - auto-detection across all WSL distributions, WSL SDKs in the SDK dropdown, and full support across Run, REPL, Notebook, Debugger, LSP, Profiler, Formatter, and Package Manager
So, as discussed - two big features in this one.
The Package Creation Wizard walks you through scaffolding a new Julia package step by step. Pick a preset - Basic for something minimal, Documented if you want Documenter.jl baked in, Full for the kitchen sink, or Custom to cherry-pick. Add test/docs/examples sub-projects, choose your license, configure CI, add plotting dependencies.
And for Windows users: WSL support is finally here. The plugin now auto-detects Julia installations across all your WSL distributions. Once detected, WSL SDKs show up in the dropdown just like native installations.
@ufechner7: Thanks for the package wizard idea - I bet it’ll help many newcomers!
@jdad: Thanks to you, we can all enjoy full WSL support now
Let me know if you find any issues with either of this. You can find the new release here (Install via File - Settings - Plugins - Install from Disk): https://plugins.jetbrains.com/plugin/download?rel=true&updateId=1076616 , or as always, wait till maybe Monday for JetBrains to release this through the official channels.
