# Julia VS Code extension version v0.16 released

**URL:** <https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692>\
**Category:** VS Code\
**Created:** [June 18, 2020, 7:26pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692 "2020-06-18T19:26:33Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [June 24, 2020, 9:58am UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/26 "2020-06-24T09:58:18Z")

</div>

So, what is the current state and planning development of IDEs for Julia? I remember to have read some time ago that the current VS-Code Julia plugin had different objectives than Juno, and that a VS-Code based Juno was planned, but I understood now that instead the two projects merged, right ?  
Also, what still “classical Juno” has that the current VS Code plugin misses ?

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [June 24, 2020, 3:00pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/27 "2020-06-24T15:00:10Z")

</div>

> [@anon68507720](#):
>
> did you see my last two feedback posts?

I did. We’ll hopefully fix most of those issue in the next release.

> [@sylvaticus](#):
>
> So, what is the current state and planning development of IDEs for Julia? I remember to have read some time ago that the current VS-Code Julia plugin had different objectives than Juno, and that a VS-Code based Juno was planned, but I understood now that instead the two projects merged, right ?

Yup. Turns out our respective visions were much more compatible than we originally thought.

The Atom-based Juno is in maintenance-only mode now.

> [@sylvaticus](#):
>
> Also, what still “classical Juno” has that the current VS Code plugin misses ?

Take a look at the [`juno-parity` label](https://github.com/julia-vscode/julia-vscode/labels/juno-parity). The biggest missing features probably are the

- documentation browser,
- profiler UI, and
- a more fully featured plot pane.

Apart from that there’s a bunch of additional QoL enhancements that I’d like to see, but that takes a lot of time and feedback.

---

<div class="post-metadata">

**Author:** ![cortner](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cortner/32/204_2.png) [@cortner](https://discourse.julialang.org/u/cortner)\
**Post date:** [June 27, 2020, 4:17pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/29 "2020-06-27T16:17:47Z")

</div>

Is there any way to have the REPL in a vertical side panel instead of a horizontal tab at the bottom?

---

<div class="post-metadata">

**Author:** ![CameronBieganek](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cameronbieganek/32/6915_2.png) [@CameronBieganek](https://discourse.julialang.org/u/CameronBieganek)\
**Post date:** [June 27, 2020, 4:28pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/30 "2020-06-27T16:28:28Z")

</div>

@cortner Right click on the top edge of the panel and there is an option to change the location of the panel. The VS Code developers kind of hid that feature. I think there used to be a button for it.

It looks like it’s also in the menu under View \> Appearance \> Move Panel Left/Right.

---

<div class="post-metadata">

**Author:** ![cortner](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cortner/32/204_2.png) [@cortner](https://discourse.julialang.org/u/cortner)\
**Post date:** [June 27, 2020, 5:07pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/31 "2020-06-27T17:07:53Z")

</div>

Thanks - can’t believe I missed that.

Now my only remaining gripe is that the REPL isn’t in the same panel as the browser and the git pane. (it is really convenient in Atom to just cycle through these) but I’m guessing this is all outside the control of the Julia 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 27, 2020, 5:19pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/32 "2020-06-27T17:19:05Z")

</div>

> [@cortner](#):
>
> Now my only remaining gripe is that the REPL isn’t in the same panel as the browser and the git pane.

You can just drag and drop it to the sidebar: click on the `TERMINAL` text, and drag it where you want it.

---

<div class="post-metadata">

**Author:** ![DNF](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dnf/32/10191_2.png) [@DNF](https://discourse.julialang.org/u/DNF)\
**Post date:** [June 27, 2020, 6:10pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/33 "2020-06-27T18:10:43Z")

</div>

> [@CameronBieganek](#):
>
> The VS Code developers kind of hid that feature. I think there used to be a button for it.

Yes, there was a button that was removed long ago. Extremely weird that vertical isn’t the default, BTW, and on top of that it’s hidden. Bizarrely, it even took a long time to get a vertical terminal in the first place(!)

---

<div class="post-metadata">

**Author:** ![ajkeith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ajkeith/32/970_2.png) [@ajkeith](https://discourse.julialang.org/u/ajkeith)\
**Post date:** [June 27, 2020, 7:57pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/34 "2020-06-27T19:57:04Z")

</div>

Very cool, I did not know you could do that! Is there also a way to move the terminal to the bottom right quadrant instead of taking the full vertical height? With normal VS Code panes you can split the height but as far I can tell the terminal pane can only be split with output/terminal/problems/debug. I checked through the juno parity labeled issues but didn’t see that. I assume this would be a VS Code capability not a Julia extension capability so maybe not appropriate to open an issue for the Julia 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 27, 2020, 8:31pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/35 "2020-06-27T20:31:09Z")

</div>

I don’t think you can split. Yeah, no need for an issue with us, this kind of stuff is out of our control.

---

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [June 28, 2020, 7:32pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/36 "2020-06-28T19:32:41Z")

</div>

Yea, I don’t understand why VS code, that is pretty recent, didn’t go for an approach “put this panel wherever you want” à la Atom…

---

<div class="post-metadata">

**Author:** ![laborg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/laborg/32/5474_2.png) [@laborg](https://discourse.julialang.org/u/laborg)\
**Post date:** [June 29, 2020, 5:10am UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/37 "2020-06-29T05:10:40Z")

</div>

Checkout the latest VScode updates for flexible view and panel layout:

> **[Visual Studio Code May 2020](https://code.visualstudio.com/updates/v1_46#_flexible-layout)**
>
> Learn what is new in the Visual Studio Code May 2020 Release (1.46)

---

<div class="post-metadata">

**Author:** ![DNF](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dnf/32/10191_2.png) [@DNF](https://discourse.julialang.org/u/DNF)\
**Post date:** [June 29, 2020, 7:36am UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/38 "2020-06-29T07:36:33Z")

</div>

> [@sylvaticus](#):
>
> I don’t understand why VS code […]

I don’t really know (so speculating here), but increased flexibility often comes at the price of reduced performance. Atom was criticized a lot over performance issues, and I wouldn’t be surprised if its very high degree of flexibility made performance optimization harder.

---

<div class="post-metadata">

**Author:** ![ajkeith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ajkeith/32/970_2.png) [@ajkeith](https://discourse.julialang.org/u/ajkeith)\
**Post date:** [June 29, 2020, 3:35pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/39 "2020-06-29T15:35:16Z")

</div>

It looks like more flexible terminal windowing is discussed in [vscode#10546](https://github.com/microsoft/vscode/issues/10546) which is the [second most liked](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) issue for vscode. The May updates that @laborg mentioned are very cool and it seems like there’s active development on #10546, so I think there’s a good chance that it will be addressed.

---

<div class="post-metadata">

**Author:** ![Imi\_Kim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/imi_kim/32/9699_2.png) [@Imi\_Kim](https://discourse.julialang.org/u/Imi_Kim)\
**Post date:** [September 21, 2020, 1:19pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/40 "2020-09-21T13:19:24Z")

</div>

For inline evaluation, I am not able to select anything to copy / paste (clipboard) inside the inline result.

This is os x 10.14.6 and vs code 1.49 and julia 1.5.1 and extension 1.0.7.

Sorry if this has been answered elsewhere, I could not find it.

---

<div class="post-metadata">

**Author:** ![j2b2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j2b2/32/3387_2.png) [@j2b2](https://discourse.julialang.org/u/j2b2)\
**Post date:** [March 12, 2021, 11:35am UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/41 "2021-03-12T11:35:11Z")

</div>

Hi, same problem, where is an answer ?

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [March 12, 2021, 11:36am UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/42 "2021-03-12T11:36:36Z")

</div>

You can only select and copy text in the hover pop-up (which works fine for me on Linux). The actual inline-result bubbles are unselectable.

---

<div class="post-metadata">

**Author:** ![j2b2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j2b2/32/3387_2.png) [@j2b2](https://discourse.julialang.org/u/j2b2)\
**Post date:** [March 12, 2021, 11:40am UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/43 "2021-03-12T11:40:34Z")

</div>

Thanks for this quick answer ! The problem is with “large” arrays (~ more than 20 elements)

---

<div class="post-metadata">

**Author:** ![j2b2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j2b2/32/3387_2.png) [@j2b2](https://discourse.julialang.org/u/j2b2)\
**Post date:** [March 12, 2021, 11:46am UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/44 "2021-03-12T11:46:45Z")

</div>

And about the title of this conversation (“v0.16 released” :-), [Home · Julia in VS Code](https://www.julia-vscode.org/docs/stable/) displays “Whats New Version v0.17 Version v0.16”… That said many thanks for this fantastic work.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [March 12, 2021, 11:49am UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/45 "2021-03-12T11:49:33Z")

</div>

I don’t think we have a good solution for that. You can just call `clipboard` on your object though. Or, if you want the normal display, something like

```julia-auto
function show_clipboard(x)
    io = IOBuffer()
    show(io, "text/plain", x)
    clipboard(String(take!(io)))
end

```

> [@j2b2](#):
>
> And about the title of this conversation (“v0.16 released” :-), [Home · Julia in VS Code](https://www.julia-vscode.org/docs/stable/) displays “Whats New Version v0.17 Version v0.16”… That said many thanks for this fantastic work.

We do have newer release threads:

> [@\[ANN\] VS Code extension 1.1 released](https://discourse.julialang.org/t/ann-vs-code-extension-1-1-released/54896):
>
> We just released version 1.1 of the [Julia extension for VS Code](https://www.julia-vscode.org/) to the marketplace. As always, you don’t need to do anything to get the new release, auto-update should take care of that. This release has only two new user-level features, but a massive amount of improvements under the hood. We also fixed a lot of bugs, so hopefully it will provide a smoother experience. Here are the release highlights: We added a documentation browser. This provides a more permanent home for documentation in …

Should just remove the “What’s new” section and point to the changelog, I suppose.

---

<div class="post-metadata">

**Author:** ![j2b2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j2b2/32/3387_2.png) [@j2b2](https://discourse.julialang.org/u/j2b2)\
**Post date:** [March 12, 2021, 12:02pm UTC](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692/46 "2021-03-12T12:02:15Z")

</div>

Many thanks, your function `show_clipboard()` is magical !

[Previous page](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-16-released/41692.md?page=1)