# \[ANN\] Julia for VS Code 1.5 released
**URL:** https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365
**Category:** VS Code
**Tags:** announcement, vscode
**Created:** [November 12, 2021, 8:22am UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365 "2021-11-12T08:22:13Z")
**Posts on this page:** 18
**Page:** 3
### Author:  [@rafael.guerra](https://discourse.julialang.org/u/rafael.guerra)
#### Post date: [November 18, 2021, 10:53am UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/42 "2021-11-18T10:53:22Z")
> [@Oto\_Brzobohaty](#):
>
> I used ctrl+enter to execute “active” line, and it worked even in the for loop body. Now, I can use shift + enter or ctrl + enter, but both commands execute a whole for loop. The same for function.
>
> Is there a way how to get the previous behaviour?
The answer seems to be [provided in post above](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/24).
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [November 18, 2021, 11:15am UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/43 "2021-11-18T11:15:32Z")
> [@mschauer](#):
>
> Can you edit with a link? That would be helpful.
I’ve added a link to the definitions, but YMMV on whether that’s gonna be helpful.
---
### Author:  [@Oto\_Brzobohaty](https://discourse.julialang.org/u/Oto_Brzobohaty)
#### Post date: [November 18, 2021, 11:53am UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/44 "2021-11-18T11:53:48Z")
> [@pfitzseb](#):
>
> ```julia
> {
> "key": "Ctrl+Enter",
> "command": "-language-julia.executeCodeBlockOrSelection"
> },
> {
> "key": "Ctrl+Enter",
> "command": "language-julia.executeJuliaCodeInREPL"
> }
>
> ```
You are right, thank you.
---
### Author:  [@CameronBieganek](https://discourse.julialang.org/u/CameronBieganek)
#### Post date: [November 18, 2021, 1:53pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/45 "2021-11-18T13:53:08Z")
I’m testing out the new key bindings to see if I can get used to them, but I’ll probably go back to the old Ctrl + Enter. Old habits die hard. And I prefer the simple conceptual model of sending code directly to the REPL, which I first encountered in RStudio. And of course moving the cursor is essential.
---
### Author:  [@eirikeb](https://discourse.julialang.org/u/eirikeb)
#### Post date: [November 18, 2021, 4:58pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/46 "2021-11-18T16:58:20Z")
Looks great! Is there a VS Code version requirement somewhere that I’m missing? Working on a remote server with an old VS Code version (1.56.2) and can’t find any more recent version than 1.28.8, and wondering if it’s the firewall, the VS Code, or something else that’s wrong…
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [November 18, 2021, 4:59pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/47 "2021-11-18T16:59:00Z")
Yeah, this version of the extension needs VS Code 1.60.1 at least.
---
### Author:  [@lmiq](https://discourse.julialang.org/u/lmiq)
#### Post date: [November 18, 2021, 5:12pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/48 "2021-11-18T17:12:50Z")
> [@pfitzseb](#):
>
> The plot pane is now interactive – you can zoom and pan plots (hold Alt/Option for that functionality)
I am on Linux, and I cannot figure out how to zoom etc the plots. alt moves the whole windows, “Option” (is it the “windows key”?) opens the main menu.
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [November 18, 2021, 5:38pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/49 "2021-11-18T17:38:48Z")
> [@lmiq](#):
>
> alt moves the whole windows
That’s something you’ll have to tell your window manager to stop doing, I think.
---
### Author:  [@lmiq](https://discourse.julialang.org/u/lmiq)
#### Post date: [November 18, 2021, 5:45pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/50 "2021-11-18T17:45:12Z")
> [@pfitzseb](#):
>
> That’s something you’ll have to tell your window manager to stop doing, I think.
Yes, that works 🙂 .
---
### Author:  [@lmiq](https://discourse.julialang.org/u/lmiq)
#### Post date: [November 18, 2021, 5:54pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/51 "2021-11-18T17:54:22Z")
I started having this error now, when using the “Tag new version” option:
```julia
ERROR: type `VersionNumber` is not a valid TOML type, pass a conversion function to `TOML.print`
Stacktrace:
[1] error(s::String)
@ Base ./error.jl:33
[2] _print(f::Nothing, io::IOStream, a::Dict{String, Any}, ks::Vector{String}; indent::Int64, first_block::Bool, sorted::Bool, by::Function)
@ TOML.Internals.Printer /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.6/TOML/src/print.jl:112
[3] #print#13
@ /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.6/TOML/src/print.jl:170 [inlined]
[4] print(io::IOStream, a::Dict{String, Any})
@ TOML.Internals.Printer /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.6/TOML/src/print.jl:170
[5] (::PkgDev.var"#6#13")(f::IOStream)
@ PkgDev ~/.julia/packages/PkgDev/jqw0f/src/tag.jl:158
[6] open(::PkgDev.var"#6#13", ::String, ::Vararg{String, N} where N; kwargs::Base.Iterators.Pairs{Union{}, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
@ Base ./io.jl:330
[7] open
@ ./io.jl:328 [inlined]
[8] tag_internal(package_name::String, pkg_uuid::String, pkg_path::String, version::Symbol; registry::Nothing, release_notes::Nothing, credentials::String, github_username::String)
@ PkgDev ~/.julia/packages/PkgDev/jqw0f/src/tag.jl:157
[9] tag(package_path::FilePathsBase.PosixPath, version::Symbol; kwargs::Base.Iterators.Pairs{Symbol, String, Tuple{Symbol, Symbol}, NamedTuple{(:credentials, :github_username), Tuple{String, String}}})
@ PkgDev ~/.julia/packages/PkgDev/jqw0f/src/tag.jl:32
[10] top-level scope
@ ~/.vscode/extensions/julialang.language-julia-1.5.5/scripts/packagedev/tagnewpackageversion.jl:29
FINISHED
```
Does it may have anything to do with some extension upgrade?
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [November 18, 2021, 6:02pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/52 "2021-11-18T18:02:05Z")
Maybe, although I’m not aware of any relevant code having changed. Might also be related to you upgrading your Julia version. Please open an issue.
---
### Author:  [@cscherrer](https://discourse.julialang.org/u/cscherrer)
#### Post date: [December 1, 2021, 4:06pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/53 "2021-12-01T16:06:18Z")
> [@pfitzseb](#):
>
> Just add
>
> ```julia
> {
> "key": "Ctrl+Enter",
> "command": "-language-julia.executeCodeBlockOrSelection"
> },
> {
> "key": "Ctrl+Enter",
> "command": "language-julia.executeJuliaCodeInREPL"
> }
>
> ```
>
> to your keybindings.
Thanks @pfitzseb . This still took me a while to figure out. The file you need is `keybindings.json`, but VS Code doesn’t make this so easy to get to. In case it’s not obvious for others, this is `ctrl-p` then “keyboard shortcuts (JSON)”.
---
### Author:  [@Klaas\_Pauly](https://discourse.julialang.org/u/Klaas_Pauly)
#### Post date: [December 1, 2021, 4:53pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/54 "2021-12-01T16:53:12Z")
I don’t think it’s even really necessary to open the JSON file and edit there. I’ve been able to configure it back to my preference by editing the list under the keyboard shortcuts in the menu as advised in the other post linked here (gear icon in the lower left → keyboard shortcuts).
> [@VS Code Keybinding](https://discourse.julialang.org/t/vs-code-keybinding/71992/2):
>
> Yes, in File-\>Preferences-\>Keyboard Shortcuts, add Ctrl-Enter to Julia: Send Current Line or Selection to REPL and remove it from the conflicting Julia command. I agree that this is useful action and having a keyboard shortcut in the default settings would be a good thing
---
### Author:  [@cscherrer](https://discourse.julialang.org/u/cscherrer)
#### Post date: [December 1, 2021, 6:18pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/55 "2021-12-01T18:18:01Z")
Hmm, yeah and I just realized editing the JSON breaks other uses of ctrl-enter, like finalizing a git commit. I’ll try your suggestion, maybe that’s better
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [December 1, 2021, 6:29pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/56 "2021-12-01T18:29:03Z")
True. Just add `"when": "editorTextFocus && activeEditor != workbench.editor.notebook && editorLangId == julia || editorLangId == juliamarkdown"`to the new keybinding to fix that.
---
### Author:  [@rafael.guerra](https://discourse.julialang.org/u/rafael.guerra)
#### Post date: [March 17, 2023, 8:39pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/57 "2023-03-17T20:39:06Z")
> [@CameronBieganek](#):
>
> but I’ll probably go back to the old Ctrl + Enter. Old habits die hard.
`Ctrl + Enter` stopped working for me. Before it was executing the code at the cursor line (+ sending to the REPL) and then moving to the next line. I am no longer able to retrieve this behavior. Any clues?
---
### Author:  [@CameronBieganek](https://discourse.julialang.org/u/CameronBieganek)
#### Post date: [March 17, 2023, 11:16pm UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/58 "2023-03-17T23:16:27Z")
I’ve been using the default `Shift + Enter` these days. It seems to work fine. The only downside is that the code doesn’t get colorized by OhMyREPL. I seem to recall that with the old `Ctrl + Enter` the code did get colorized by OhMyREPL.
---
### Author:  [@rafael.guerra](https://discourse.julialang.org/u/rafael.guerra)
#### Post date: [March 18, 2023, 12:23am UTC](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365/59 "2023-03-18T00:23:41Z")
@CameronBieganek, thanks.
I’ve been fooled again by the bad habit of keeping very long catch-all scripts, where I test things and don’t clean them up. After a few thousand lines there must be some stuff that confuses the Julia extension (and me for that matter).
Starting on a blank page fixed it.
[Previous page](https://discourse.julialang.org/t/ann-julia-for-vs-code-1-5-released/71365.md?page=2)