# Juno keybindings stopped working in VSCode
**URL:** https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552
**Category:** VS Code
**Created:** [July 13, 2021, 7:46am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552 "2021-07-13T07:46:09Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@nilshg](https://discourse.julialang.org/u/nilshg)
#### Post date: [July 13, 2021, 7:46am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/1 "2021-07-13T07:46:09Z")
Had another go at switching to VSCode yesterday, and somehow managed to make the experience worse: I’m using the Juno keybindings from [here](https://gist.github.com/kescobo/3bc5416d83343ebe53da73813d4a61e6) in my `keybindings.json`, but for some reason they’ve stopped working.
WIth an empty `keybindings.json`, I can select a line of code and evaluate it with `Ctrl+Enter`, however this seems to send the line to the REPL and evaluate there, despite me having set result mode to “inline”.
Once I add either of the two `Ctrl+Enter` keybindings to my settings:
```julia
{
"key": "ctrl+enter",
"command": "language-julia.executeCodeBlockOrSelection",
"when": "editorTextFocus && editorLangId == 'julia'"
}
```
or
```julia
{
"key": "ctrl+enter",
"command": "-language-julia.executeJuliaCodeInREPL",
"when": "editorTextFocus && editorLangId == 'julia'"
}
```
`Ctrl+Enter` stops to work entirely, i.e. selecting a line an pressing it doesn’t do anything. I uninstalled VSCode and nuked every related folder, but after reinstalling from scratch the problem persists. I’m on:
```julia
julia> versioninfo()
Julia Version 1.7.0-beta3.0
Commit e76c9dad42 (2021-07-07 08:12 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-12.0.0 (ORCJIT, skylake)
Environment:
JULIA_EDITOR = code
JULIA_NUM_THREADS
```
Has anybody seen this? Any ideas where I’m going wrong here?
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [July 13, 2021, 7:49am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/2 "2021-07-13T07:49:10Z")
I doubt this is related to keybindings. Can you check whether Alt+Enter works with unmodified keybindings?
---
### Author:  [@nilshg](https://discourse.julialang.org/u/nilshg)
#### Post date: [July 13, 2021, 7:53am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/3 "2021-07-13T07:53:07Z")
Nope, doesn’t do anything, neither with code selected nor with the cursor in some code block. I should also have mentioned that I am stuck at `Starting Julia Language Server...`, but I thought this would be unrelated as I can use Ctrl+Enter to evaluate, but maybe not?
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [July 13, 2021, 7:54am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/4 "2021-07-13T07:54:00Z")
No, we need the LS running to figure out which code block to run. Can you check Outputs \> Julia Language Server for errors?
---
### Author:  [@nilshg](https://discourse.julialang.org/u/nilshg)
#### Post date: [July 13, 2021, 7:55am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/5 "2021-07-13T07:55:51Z")
Not 100% sure what that means - is it just the terminal window at the bottom, going to the “Output” tab and then selecting Julia Language Server trace in the dropdown?
That seems to be emtpy…
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [July 13, 2021, 7:56am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/6 "2021-07-13T07:56:48Z")
You’re looking at the wrong one:
---
### Author:  [@nilshg](https://discourse.julialang.org/u/nilshg)
#### Post date: [July 13, 2021, 7:57am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/7 "2021-07-13T07:57:21Z")
Hm, I don’t seem to have that:
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [July 13, 2021, 7:57am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/8 "2021-07-13T07:57:45Z")
Ah. That’s bad. Can you double check that you have the Julia path set correctly?
---
### Author:  [@nilshg](https://discourse.julialang.org/u/nilshg)
#### Post date: [July 13, 2021, 8:01am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/9 "2021-07-13T08:01:21Z")
I have no path set:
which I suppose means it picks up whatever is on `PATH` for `julia`? In a normal terminal I get
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [July 13, 2021, 8:04am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/10 "2021-07-13T08:04:37Z")
Ah, you’re on 1.7. The extension doesn’t support that yet, unfortunately. Could’ve just read your `versioninfo()` above…
---
### Author:  [@nilshg](https://discourse.julialang.org/u/nilshg)
#### Post date: [July 13, 2021, 8:12am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/11 "2021-07-13T08:12:47Z")
Again, Juno is ahead of the curve 🙂
Is this a general rule that VSCode doesn’t support beta/nightly releases or is there something special about 1.7?
---
### Author:  [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)
#### Post date: [July 13, 2021, 8:43am UTC](https://discourse.julialang.org/t/juno-keybindings-stopped-working-in-vscode/64552/12 "2021-07-13T08:43:56Z")
We don’t officially support betas/nightlies, but are usually pretty good about at least not failing quite as drastically on them. The required fix should already be merged, so the insiders build should work.