I have a weird behavior with the '3' key of my MB Air keyboard in VS Code in Ruby and Elixir files only: instead of '3' it displays '#' character.
I've already looked and checked everywhere in the settings, - nothing.
In all other file extensions it works as needed (JSON, YALM, Java, etc.) but miserably fails in *.rb and *.exs files.
VS Code version:
Version: 1.65.1 (Universal)
Commit: 8908a9ca0f221f36507231afb39d2d8d1e182702
Date: 2022-03-08T02:20:11.670Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 21.3.0
Related
Recently i am not able to use the Vlocity VScode extension. I tried to uninstall the extension and salesforce one and then VS code also. Reinstalled everything from scratch and able to work with Salesforce extension but not able to connect the org for vlocity. Even cleaned the alias and logged out from all the orgs in terminal and started with just one org but no luck. I am attaching the screenshot. Please let me know if there is something that is missing from my end or if this is a known issue.
OS : MAC (12.6.1) Monterey
SF cli : sfdx-cli/7.180.0 darwin-x64 node-v18.12.1
Vs Code Version : 1.74.0 (Universal)
Commit: 5235c6bb189b60b01b1f49062f4ffa42384f8c91
Date: 2022-12-05T16:43:37.594Z (1 wk ago)
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 21.6.0enter image description here
I am following this tutorial:
https://code.visualstudio.com/docs/remote/ssh-tutorial
I have the extension installed..
And I can see the green button
But when I look for the Remote-SSH command in the search bar that pops up, I cannot find it
Am I missing a step?
This is my vs code version info
Version: 1.67.2 (Universal)
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:20:57.384Z (4 mos ago)
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Darwin x64 19.6.0
For some reason command+shift+p brings up the menu with > Remote Connection shown, but the green button does not. Not sure what the difference is.
I've installed the ARM version of VSCode V1.67.2 on my iMac M1 (see below). However I can't seem to get many extensions to work.
For example, I install 'pico-go' and then issue the command 'Pico-Go > Configure Project' and immediately get:
"Command 'Pico-Go . Configure project' resulted in an error (command 'picogo.initialise' not found)"
Same basic error with the Pymakr extension and many other extensions.
(On the other hand Espressif and PlatformIO seem to work!)
This seems to be a fundamental issue with my installation rather than an extension-specific issue so any assistance would be appreciated.
Susan
Version: 1.67.2
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:20:04.972Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Darwin arm64 21.5.0
I have probably around 25 odds extensions installed on my VSCode.
However some of my extensions are disabled - they seems to change a bit every time I start the VSCode and there is no option to enable it.
The only work around I have at the moment is to uninstall and install again to get it enabled.
I don't see any pattern. Why is this the case?
VSCode version:
Version: 1.47.3 (system setup)
Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
Date: 2020-07-23T13:12:49.994Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19042
Though not obvious to end users like you, each extension releases has a minimal VSCode version required.
For example, the Microsoft C/C++ extension showed in your screen shot is of version 1.5.1, which depends on VSCode 1.53.0 and above,
"engines": {
"vscode": "^1.53.0"
},
https://github.com/microsoft/vscode-cpptools/blob/1.5.1/Extension/package.json#L14
Since you are using a much older version (1.47.3), this extension can only be disabled to avoid conflicts.
Using version listed below. Have the experimental feature turned on, Debug button was there on the toolbar at 1 time now it's gone? Is anyone else using this feature yet?
"jupyter.experimental.debugging": true,
Version: 1.59.0-insider (user setup)
Commit: 50b3811fdc5b5c80ca516a2edfffedcbd464b033
Date: 2021-07-15T05:13:58.348Z
Electron: 13.1.6
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Windows_NT x64 10.0.19043
I had the same problem. I played a bit around and found out that ipykernel in version 6.2 or higher is necessary to get debugging running. I only had version 5.3.8 installed. Also I was a bit confused, because there is no debug symbol. The feature is called "Run by line". You can also have a lock at:
https://github.com/microsoft/vscode-jupyter/wiki/Setting-Up-Run-by-Line-and-Debugging-for-Notebooks
https://code.visualstudio.com/docs/python/jupyter-support-py#_debug-a-jupyter-notebook
As a workaround I exported my notebook to a python skript. There debugging was working as usual.