VS Code extension v0.8.0-beta.1 release

If it’s all underlined red but you can execute the code in your file them something is majorly wrong on our (CSTParser) side. If you can narrow it down to a mwe I should be able to stick up a fix

This screenshot sums it up I think.
So I started with an empty file.
Added the using statements. Then the for loop and while typing it julia changed to be busy.

The problem message shows (I guess) that it went to busy after typing f and then got stuck there.

Are you sure you are running v0.8? Sometimes v0.7 sticks around.

vscode-julia-2

If I click on Reload nothing changes therefore I suppose it is already working and just has some issues with the beta, correct?

No, it means it is not working. Go to your .vscode/extensions folder, deleta all julialang* folders and reinstall the beta.

Alright. Thanks it seems to work perfectly. Even if I get lots of errors because of JuMP variables.

x1 is undefined but it’s the normal declaration in JuMP.

@variable(m, 0 <= x1 <= 1.38629436111989)

Thanks again!

I took a look. Still not clear what the problem is, but you can display figures by calling gcf() in the REPL. I think for the v0.8.0 release that will have to be good enough, but I’m trying to figure out what we can do for the next release/more long term.

Thanks. Works for me!

And we have a release candidate:

https://github.com/JuliaEditorSupport/julia-vscode/releases/tag/v0.8.0-rc.2

Please test it and report any issues, bugs etc.

Once we have a RC without major bugs we’ll cut a final release, hopefully in a few days.

3 Likes

And we have RC3 with a couple more bugs fixed:

https://github.com/JuliaEditorSupport/julia-vscode/releases/tag/v0.8.0-rc.3

1 Like

And we have a fourth release candidate, please test and report any bugs:

https://github.com/JuliaEditorSupport/julia-vscode/releases/tag/v0.8.0-rc.4

F12 - Jump to definition doesn’t seem to work. It worked once I can’t remember in which version.
Btw is there a way to get a list of all functions?

It works, but you have to initially wait for the language server to do its thing. So in the beginning it says Julia Language Server is busy, but after that it should work.

It says: Julia: ready but nothing is happening if I press F12
I restarted VS Code and after a long while it started to work again…

I don’t think you have the newest version of the extension. The newest version says only Julia Language Server is busy when it’s busy and nothing otherwise.

It does now. Maybe the reload after I installed via vsix didn’t work. Thanks. I’ll keep you updated if it stops working :wink:

And we have a fifth release candidate:

https://github.com/JuliaEditorSupport/julia-vscode/releases/tag/v0.8.0-rc.5

Thanks everyone for testing, please keep reporting any bugs and issues you run into!

3 Likes

And here is RC 6:

https://github.com/JuliaEditorSupport/julia-vscode/releases/tag/v0.8.0-rc.6

Hopefully this will be the last one and we can release those bits on Mon as the final bits to the marketplace!

Beginners question: How do I launch a Julia terminal? In the moment I just launch a bash console and the start Julia. Is there a better way?

That’s what I do. On Windows 10: start git bash in the terminal, and then fire up julia.
That gives me a usable shell on Windows (which I’m not going to get with Julia started from CMD).