Hmm, I’m afraid that I still can’t make it work. It still stalls with Julia Process and when I change it to Text I see this error.
You mean, to do the using? It works fast on the normal REPL (I mean, that in PyCharm).
The DISPLAY_IN_VSC? I added it so one can display in VSC plot pane & Notebook (that is the default), or if set to “no” the display shows up in a floating figure.
I got another idea… which OS are you on?
Windows
Yeah. I think that is why. I am currently trying to reproduce it all, hence why I haven’t responded yet. But am on it 
@joa-quim: I finally managed to fully recreate all of your issues locally and fix them.
So now GMT loads:
I did have to also update my code for it so that I am using the same ENV hook you implemented for vscode and also support streamed images, rather than exported files. But it works now!
I will finish up some pending work on other bugfixes and then submit an update later today
You must have had a lot of work given the time you took this time
I see that you add Ghostscript_jll? Why so? It’s a GMT.jl dependency so you should not have needed to do it. But on the other hand there is something broken in it on Windows. If Julia is not in the path (which happens when installed via juliaup) a libz.dll error raises up. Did you cross with that problem?
Yes, exactly - I hit the libz.dll issue you’re describing, and that’s the whole reason why I ended up down the Ghostscript_jll rabbit hole. The plugin does NOT depend on Ghostscript_jll. The message in my screen was only for me during debugging.
The actual requirement is either:
Other issues I ran into: GMT is really heavy with lots of transient dependencies. That broke some of my other dependencies in my test project and also caused a bunch of troubles during test runs…
Sorry to hear that you had all those troubles. Regarding the Ghostscript, I brought it up here Juliaup breakes GMT (via Ghostscript and tmp dir permissions) but it went up unnoticed. I must report it as a bug.
Hmm, can you elaborate a bit more (or open issues i GMT.jl repo)? GMT has only 2 non-stdlibs or *.jll.: Tables and PrecompileTools, so a very minimalist depends chain. What do you mean by: transient dependencies?
I can’t remember the details, but some broke during the notebook session, because another dependency of mine was already including Plots. And I also bumped into issues in combination with Makie and others - chances are those aren’t related though. After a cleanup of the dependencies everything was okay.
The most time I spent on a precompilation issue though. I must have had some bad luck during one of my trials, and afterwards the old stale pids were still left behind. So GMT would never even complete precompilation. I ended up adding a new tool action for us that cleans up these stale pids (that are not bound by an ongoing julia session) - you can find it under Tools - Julia - and also added a check for them during REPL startup.
Lastly: Notebook kernel runs are super slow (you noticed the same problem) because of the precompilation - it is an entirely new session each time, for better or worse, but it means packages need to be reinstalled, which took super long in my case. There was also no indicator other than the top right one that hte session was still ongoing. I now switched the defaults to REPL session and added a cell execution timer underneath the cell that should display during its run.
Ah, I see. GMT, Plots and Makie share several plotting function names, and that may lead to many name clashes if not prefixed.
The precompilations in Julia have been a long time mystery to me. Starting a session on REPL where a precomp cache exists takes ~0.7 sec for me. But (almost)anything else than the normal REPL triggers compilations like crazzy.
I think one of the benefits of doing this project for me is that I get to download, try out and sometimes even understand (parts of) the sources of other Julia projects. It is quite cool actually - so the detour was a welcomed one…
New Release: Flexible Julia 2026.9.18
New Features:
Changes:
Fixes:
include chains (#105)More notebook polish. Live stdout streaming means you actually see println output as it happens instead of all at once. GMT.jl inline rendering is fixed properly now, and the kernel no longer hangs during heavy package loads.
Switched the default notebook kernel to REPL so it reuses your existing Julia session - faster startup and shared state.
Also enabled “Break on error” by default in the debugger. You can still turn it off, but most people seem to want it on.
@joa-quim: Thanks for the continued GMT.jl feedback!
@mvscheven: Appreciate the reports on method overloads and Variables panel duplicates!
@ufechner7: Thanks for the doc-link and include chain fixes!
Gave it a quick test and it works (bravo) but …
You should be able to either scroll down to see the rest of it - or see it in the plots panel In the Julia tab. The rest I will fix for Monday (I got some family event to attend).
Thanks!
Man, take the whole week for that
Release 2026.9.18 - 2026.9.20 have been approved just now, after being stuck in a feedback loop (there was a false flag on some IDE compatibility check that has now been resolved).
Release 2026.9.20 was just a quick bugfix release improving and hopefully finally fixing all native on-hover documentation:
P.S: Family gathering was of course a delight
hello! I’m new both to Julia (need to quickly learn it to get a bunch of things done) and also fairly new to IntelliJ IDE’s, however I’ve crafted a pile of Rust code using Rustrover lately so I think I got the hang of basic use.
Here’s some first impressions of the FlexibleJulia plugin, note that I don’t know Julia virtually at all.
first, automatic code indentation looks wonky to me. I’m not familiar with the recommended style for Julia, but here’s how the Flexiblejulia plugin formats some trivial(?) little code and it seems off to me:
module Testing
struct Asdf
asdf
qwe
end
function Foo(a, b)
a + b
end
struct Baz
qux
quux
end
export Foo
end #module
using .Testing
The same, when typed in emacs with julia-mode, letting emacs indent every line automatically, this looks more readable to me:
module Testing2
struct Asdf
foo
fooo
end
function Foo(a, b)
a * 2b
end
struct Baz
qux
quux
end
export Foo
end
using .Testing2
Then, the documentation says there’s “native .ipynb support”. My limited experience with .ipynb and Python is that i can write stuff in cells, execute them, see useful output, and that there’s basic keyboard shortcuts to execute and split cells. This works fine in my PyCharm. However, in IDEA with the plugin, the notebook looks weird and i can’t figure out how to execute a cell in any other way than the small button in the row of buttons,
Hey there.
So cool for you to join us here and good job on your first few steps! You are definitely on the right track.
Before we begin, can you please check and update to the latest release? It should be 2026.9.20 (check via File - Settings - Plugins - Installed and hit update if you see it).
So to answer your questions:
It is weird that it didn’t autoindent those structs. What happens when you press CTRL+L?
In general, you can always also use a different formatter than the inbuilt one - those are available under File - Settings - Languages - Julia. But you must install the package before using them. I will meanwhile check and probably provide a fix later today or tomorrow if I can reproduce this.
About the jupyter notebook: I reimplemented the Jupyter notebook, so that i wouldn’t have a dependency to the JetBrains one. The reason is that otherwise many users of the community edition would be left out. I also just generally dislike the idea of adding dependencies, cause not all developers like that. That explains how it looks different. Functionally it is the same language editor as the original one.
As for your Julia REPL there was a bug a few versions ago, which is why i think you need to update. It shouldn’t last longer than a few seconds and then show “idle”. Afterwards you can run the commands. You can also switch from “REPL Kernel” to a new session for the notebook (which is what the JetBrains IDE does), but those may need a bit of time to precompile. So startup is slower.
oh hi, thanks for your awesomely prompt response!
Sorry, I meant CTRL + ALT + L. It is for auto indent.
I just checked - you are right that struct doesn’t autoindent. Will fix. Our formatter is on its own quite strong and setting the JuliaFormatter by default means I need to reinstall it for those that don’t have it - so not really a good option. But happy to improve ours!
Meanwhile:
Jupyter notebook editor is the same language editor as your file editor, so the cells behave exactly as the regular file would, including code formatting. I haven’t added shortcuts for cell execution/splitting yet, but happy to do so in the next proper release (after bugfixes today).
This feedback is great, btw!
