# VS Code extension v0.12.0 beta release

**URL:** <https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420>\
**Category:** VS Code\
**Tags:** announcement\
**Created:** [June 18, 2019, 6:44pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420 "2019-06-18T18:44:41Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [June 18, 2019, 6:44pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/1 "2019-06-18T18:44:41Z")

</div>

We just released a first beta v0.12.0.beta.1 for the Julia extension for VS code [here](https://github.com/julia-vscode/julia-vscode/releases/tag/v0.12.0-beta.1). We’d much appreciate it if we could get some testers to try it out and give feedback on bugs before we release it to the marketplace.

This release brings a number of new features and fixes along:

- We added a grid viewer for tabular data. You can use it by calling the `vscodedisplay` function from the integrated REPL. You can pass pretty much any tabular data structure to that function, and then a grid view will open inside VS Code. You can also pipe tabular data into that function `data |> vscodedisplay()`. If a type either implements the [TableTraits.jl](https://github.com/queryverse/TableTraits.jl) interface, or has a `show` method for the `application/vnd.dataresource+json` MIME type, things will work with this display. The combination of these two should cover pretty much everything, so go ahead and try things like

```julia
using Queryverse

load("foo.csv") |> vscodedisplay()
load("foo.feather") |> DataFrame |> vscodedisplay()
load("foo.parquet") |> @filter(_.a>3) |> @mutate(d=_.a+_.b) |> vscodedisplay()

```

- We finished our support for julia Julia environments. Every window has an active environment, and that will now be used for all IntelliSense that is provided by the language server, all tasks will pick up that enviornment, and of course the REPL as well. When you open a folder, the extension will auto-detect if there is an environment in that folder, and if so, activate that. There is UI provided to change the active environment, and such a change will be saved in the workspace settings, so that when you open the same folder again, the choice of active environment is remembered. Feedback on the particular UI choices, defaults etc. in this space would be really valuable.
- When you run code with Alt-Enter, we no longer just paste that code into the REPL, but instead use a more sophisticated execution model. With that new model, things like `@ __DIR__ ` are properly resolved, function definitions retain accurate line numbers and the code won’t be echoed back to the REPL when you run it. This mode of code execution should also work much better with a lot of code. Ctrl-Enter is unchanged and will just copy-paste code into the REPL.
- The Weave preview was broken lately because VS Code deprecated the API we had been using for that. We migrated the Weave support to the current API, so Weave preview should work again.
- We added a test run task that outputs code coverage. If [Coverage.jl](https://github.com/JuliaCI/Coverage.jl) is installed (ideally in your global v1.1 environment), we also write a `lcov.info` file into the root folder of your workspace. This is especially useful in combination with the excellent [Coverage Gutters  
 ](https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters) VS Code extension: it can show code coverage based on `lcov.info` inside VS Code.
- We added experimental support for custom sysimages. This support has two parts: First, we added a new build task that will compile a custom sysimage for the current active environment that includes all the packages from that environment. Such a compiled sysimage is automatically stored as `JuliaSysimage.dll` (with platform specific extensions) alongside the `Project.toml` for the active environment. Second, if the `useCustomSysimage` configuration is set to `true` (the default is `false`), such a custom sysimage (if it exists and is newer than the `Manifest.toml`) will automatically be used for a new REPL session you start in VS Code. Overall this makes for a pretty smooth workflow: you can easily, with one command, compile a custom sysimage for a julia environment, and then any REPLs you start with that active environment will automatically use that sysimage. For some scenarios this can really solve a lot of the latency issues we have these days, but of course this is not perfect: building the sysimage is slow, there is no automatic rebuilding, the caching story for custom sysimages is very basic and I’m sure there are some other problems we haven’t discovered yet. So, keep in mind, this is an experimental feature! Oh, and you need to have [PackageCompiler.jl](https://github.com/JuliaLang/PackageCompiler.jl) installed for this to work, ideally in the default `v1.1` environment.
- A new command enables you to delete all plots in the plot pane.
- We now preserve the REPL focus when a figure is displayed.
- After you run the doc build task, we now open a web browser with the newly built documentation.
- We now simultaneously support vega 3,4 and 5 and vega-lite 2 and 3.
- One can now use `~` in the setting for the Julia binary.
- We fixed the `JULIA_EDITOR` functionality on Mac.
- @ZacLN fixed a _very_ large number of issues in the language server. He might also have introduced new features that I am not aware of right now, I’ll let him mention any of those, if they exist :).

If you can, please opt into the crash reporting of the extension! It makes finding and fixing bugs a lot easier for us.

To try the beta download the VSIX file from [https://github.com/julia-vscode/julia-vscode/releases/download/v0.12.0-beta.1/language-julia-0.12.0-beta.1.vsix](https://github.com/julia-vscode/julia-vscode/releases/download/v0.12.0-beta.1/language-julia-0.12.0-beta.1.vsix) and install using the `Extensions: Install from VSIX…` command.

Thanks,  
David and Zac

---

<div class="post-metadata">

**Author:** ![mbeach42](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbeach42/32/5747_2.png) [@mbeach42](https://discourse.julialang.org/u/mbeach42)\
**Post date:** [June 18, 2019, 6:50pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/2 "2019-06-18T18:50:09Z")

</div>

this is awesome, thanks!

---

<div class="post-metadata">

**Author:** ![musm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/musm/32/3675_2.png) [@musm](https://discourse.julialang.org/u/musm)\
**Post date:** [June 18, 2019, 7:12pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/3 "2019-06-18T19:12:23Z")

</div>

Thanks so much. Can you add the beta release to the VS Code extension store? I.e. add a preview package, I think other packages do something similar.

Do you know how I can ‘send to terminal’ using VS code? Instead of using the integrated terminal, I’d like to also be able to send the current file or highlighted text or a single line directly into the terminal, like in [https://github.com/randy3k/SendCode](https://github.com/randy3k/SendCode).

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [June 19, 2019, 6:20am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/4 "2019-06-19T06:20:08Z")

</div>

> [@musm](#):
>
> Can you add the beta release to the VS Code extension store?

I had looked into that at some point and I think it is too much hassle to set up. Also, there seems to be some movement to add first class support for pre-release publishing in VS Code itself, so I think our best bet is to just wait for that.

> [@musm](#):
>
> Do you know how I can ‘send to terminal’ using VS code? Instead of using the integrated terminal, I’d like to also be able to send the current file or highlighted text or a single line directly into the terminal

That doesn’t work right now, do you want to open an issue suggesting this?

---

<div class="post-metadata">

**Author:** ![jonathanBieler](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@jonathanBieler](https://discourse.julialang.org/u/jonathanBieler)\
**Post date:** [June 19, 2019, 9:50am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/5 "2019-06-19T09:50:50Z")

</div>

I’m getting a crash message form vs-code telling me the extension has crashed, without further information (I sent the info when asked though).

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [June 19, 2019, 9:57am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/6 "2019-06-19T09:57:09Z")

</div>

> [@jonathanBieler](#):
>
> I sent the info when asked though

Thanks, that is super helpful and should hopefully be enough for us to figure out what is going on!

---

<div class="post-metadata">

**Author:** ![cchderrick](https://avatars.discourse-cdn.com/v4/letter/c/ecd19e/32.png) [@cchderrick](https://discourse.julialang.org/u/cchderrick)\
**Post date:** [June 19, 2019, 6:58pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/7 "2019-06-19T18:58:15Z")

</div>

> [@davidanthoff](#):
>
> When you run code with Alt-Enter, we no longer just paste that code into the REPL, but instead use a more sophisticated execution model. With that new model, things like `@ __DIR__ ` are properly resolved, function definitions retain accurate line numbers and the code won’t be echoed back to the REPL when you run it. This mode of code execution should also work much better with a lot of code. Ctrl-Enter is unchanged and will just copy-paste code into the REPL.

When I run code by `Alt-Enter` and I press `Ctrl-C`, it doesn’t interrupt the execution, is that expected?

Thank you for all the work, this is a great extension.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [June 19, 2019, 7:34pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/8 "2019-06-19T19:34:51Z")

</div>

> [@cchderrick](#):
>
> When I run code by `Alt-Enter` and I press `Ctrl-C` , it doesn’t interrupt the execution, is that expected?

Yes… Not great, but I don’t have an idea right now how to fix this… Could you open an issue about this so that we don’t forget it?

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [June 26, 2019, 9:16am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/9 "2019-06-26T09:16:31Z")

</div>

We have a beta 2 out. It has bug fixes and one new feature: you can now run code cells (marked by `##`) with `Shift+Enter`.

Please give it a spin and report any issues back!

---

<div class="post-metadata">

**Author:** ![shorty66](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/shorty66/32/3254_2.png) [@shorty66](https://discourse.julialang.org/u/shorty66)\
**Post date:** [June 28, 2019, 11:17am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/10 "2019-06-28T11:17:15Z")

</div>

Thank you for all your work, I really appreciate that you put so much effort in this extension.  
As a daily user, i would like to buy you a beer or donate in any other way. 🍻

---

<div class="post-metadata">

**Author:** ![peters](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/peters/32/5924_2.png) [@peters](https://discourse.julialang.org/u/peters)\
**Post date:** [July 10, 2019, 1:46pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/11 "2019-07-10T13:46:06Z")

</div>

@[davidanthoff](https://discourse.julialang.org/u/davidanthoff)  
Just want to let you know there are numerous Julia programmers out there who have real benefit from the extension every day and I am one of them. Thanks for your effort.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [July 16, 2019, 10:09pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/12 "2019-07-16T22:09:51Z")

</div>

We have a first [release candidate](https://github.com/julia-vscode/julia-vscode/releases/tag/v0.12.0-rc.1)! Hopefully lots of bugs fixed and almost ready for a final release 🙂

It would be awesome if many folks could test this build and report back any bugs you find and send crash reports if asked. We hope to ship a version before Juliacon, so this is the final stretch!

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [July 18, 2019, 3:48am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/13 "2019-07-18T03:48:55Z")

</div>

And we jump straight to [RC.4](https://github.com/julia-vscode/julia-vscode/releases/tag/v0.12.0-rc.4).

At this stage, the most helpful thing for us is if as many folks as possible can install these updated release candidates and send crash reports if they come up. All the bugs we fixed lately came in via the crash reporting!

---

<div class="post-metadata">

**Author:** ![ZacLN](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zacln/32/2748_2.png) [@ZacLN](https://discourse.julialang.org/u/ZacLN)\
**Post date:** [July 18, 2019, 6:01am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/14 "2019-07-18T06:01:16Z")

</div>

I’d like to re-emphasise how useful it is for people to enable/send in crash reports. I makes fixing bugs so much easier so please do it!

---

<div class="post-metadata">

**Author:** ![peters](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/peters/32/5924_2.png) [@peters](https://discourse.julialang.org/u/peters)\
**Post date:** [July 18, 2019, 10:03am UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/15 "2019-07-18T10:03:31Z")

</div>

Ok. Installed in my laptop and ready to shoot crash reports. Thanks for the effort.

---

<div class="post-metadata">

**Author:** ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)\
**Post date:** [July 18, 2019, 12:13pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/16 "2019-07-18T12:13:38Z")

</div>

Can you please remind me which settings enable this (to the fullest extent)?

---

<div class="post-metadata">

**Author:** ![ZacLN](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zacln/32/2748_2.png) [@ZacLN](https://discourse.julialang.org/u/ZacLN)\
**Post date:** [July 18, 2019, 1:19pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/17 "2019-07-18T13:19:15Z")

</div>

Hi, adding the following to your vscode settings.json will enable it:

```julia
"julia.enableCrashReporter": true,
"julia.enableTelemetry": true,

```

Z

---

<div class="post-metadata">

**Author:** ![bernhard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bernhard/32/2619_2.png) [@bernhard](https://discourse.julialang.org/u/bernhard)\
**Post date:** [July 18, 2019, 1:26pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/18 "2019-07-18T13:26:04Z")

</div>

> [@ZacLN](#):
>
> enableTelemetry

thank you!

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [July 18, 2019, 6:25pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/19 "2019-07-18T18:25:30Z")

</div>

And we have a new release candidate 6 [here](https://github.com/julia-vscode/julia-vscode/releases/tag/v0.12.0-rc.6).

Please install and send crash reports, we are almost there!!

---

<div class="post-metadata">

**Author:** ![affans](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/affans/32/11911_2.png) [@affans](https://discourse.julialang.org/u/affans)\
**Post date:** [July 18, 2019, 7:33pm UTC](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420/20 "2019-07-18T19:33:36Z")

</div>

When is the expected release to the VScode marketplace? If it’s relatively soon, I will wait to upgrade rather than manually installing the extension.

[Next page](https://discourse.julialang.org/t/vs-code-extension-v0-12-0-beta-release/25420.md?page=2)