VS Code extension v0.11 released

announcement

#1

We released v0.11.1 of the julia VS Code extension to the marketplace.

The main feature of this release is that it supports julia 1.0, and drops support for older versions of julia.

The release also adds support for interactive PlotlyJS.jl figures in the plot pane, similar to the existing support for interactive VegaLite.jl figures. Thanks to @EricForgy for that work!

As always, thanks a lot to everyone who tested prerelease versions, reported bugs etc.!

If you do find bugs with this new release, please report them at https://github.com/JuliaEditorSupport/julia-vscode . If things work just fine, we don’t mind feedback either!

Finally, if you can, please enable crash reporting and telemetry for the extension. It really helps a lot to improve the extension.

Best,
David & Zac


#2

Thank you David and Zac for the great work you do by doing the first class integration of Julia language into VS code.


#3

Looks great. Everything works just fine. Thank you for your excellent work.


#4

Thanks!


#5

I have switched to atom Juno since 1 year ago, is vscode still a lot faster than atom? I heard the performance difference is unnoticeable now


#6

Just try it out for yourself.


#7

I just installed the extension and julia 1.03 on ubuntu 18.04 , the status bar I could see a link “Julia env: v1.0” clicking on that prompts a folder select but nothing happens after that… anyone facing the same issue ??


#8

The same here, and after closing the vscode the julia process continues to run.


#9

Right now the only thing that does is change what env gets loaded if you start a new REPL instance. We hope to improve the whole support for env much in upcoming releases, but for now that is what we’ve got…


#10

Which julia process? That is not good, maybe you could open an issue over in the repo for the extension?


#11

I tried the VS code, and it is still faster than Atom in my machine.

Interestingly, I came across an MIT licensed alternative of VSCode, VSCodium:

I feel like it is to VSCode is like what Chromium to Chrome. For those who do not like the MS license, it is worth a try.


#12

I do not know the reason but when opening the vscode the julia consumed 25% of the processing of the computer, linter and autocomplete not work, and after closing the vscode the julia continued running. After uninstalling the extension, deleting the folder and then reinstalling it, works as intended.


#13

VS code extension works quite nice for me (on Ubuntu 18.04).
But I have a little problem:
I am using PyPlot, and if I run a script by pressing F5 no diagram is displayed.
If I start Julia from the console and run the script in the console using include, it works.
Any idea what might be going wrong when pressing F5?


#14

If I enter show() I get the following message:

lia> show()
/home/ufechner/.julia/conda/3/lib/python3.7/site-packages/matplotlib/figure.py:448: UserWarning: Matplotlib is currently using agg, which is a non-GUI backend, so cannot show the figure.
  % get_backend())

julia>

#15

Maybe this issue?


#16

OK, gcf() displays the last plot in the plot plane.

But is there a way to display a PyPlot plot in a separate window?


#17

You can pop the VS Code plot plane from the multimedia display stack, and then everything should behave exactly like the normal REPL.


#18

How can I do this?


#19

I’m trying the extension on the same and its working


#20

after explicitly setting julia.executablePath its working now… thanks for the reply