Syntax errors, but no errors and code runs - visual-studio-code

Every once in a while my Visual Studio Code starts highlighting in Jupyter Notebooks syntax errors on correct code, that, indeed, runs just fine.
Example:
If I change the indentation and put everything where it was, I got the same code with different errors:
Restarting the kernel does not have any effects: as soon as the cell is run, the errors appear again. Restarting VSC solves the problem, but it is a pain in the neck to restart it every time this happens.
This is too strange to be a bug, may be it is related to some plugins I am using. Before starting to look for the responsible, is there anyone here who had and solved a similar problem?
My VSC:
Version: 1.63.2 (user setup)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:40:02.816Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043

Related

How to stop terminal rotating icon in VSC

I'm running a npm script that watches for changes and recompiles my files.
With one of the latest update, when I run this script, VSC shows in the terminal window a rotating icon signalling something is running. Good in general, but extremely distracting if the task is constantly running like in this case.
It is there any option to remove or hide this status message?
Thanks!
VSC Version: 1.57.1 (system setup)
Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
Date: 2021-06-17T13:28:07.755Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.19043
In vscode v1.59 there is a setting to disable that spinning icon animation:
The new setting terminal.integrated.tabs.enableAnimation will disable animation in the terminal tab icon. For tasks instead of a spinner the play button will be used:
I found that to return to the previous terminal behavior, I need to add the "terminal.integrated.tabs.enabled": false setting. Maybe it is an overkill, but solved my problem.

Vscode - How using %APPDATA% in settings.json?

edit - nov 2022 - I didn't need this anymore, I've switched to Linux & Docker, no more coding under Windows
Does someone knows how to refer to my APPDATA folder in my vscode settings.json file?
I'm trying to set the path to my php-cs-fixer like below so, on all my development computer, the path can be retrieved.
"php-cs-fixer.executablePathWindows": "$env:APPDATA/Composer/vendor/bin/php-cs-fixer.bat",
To be clear: $env:APPDATA seems to be unsupported.
I'm using the latest version of vscode.
Version: 1.52.1 (user setup)
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-16T16:34:46.910Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041
I tried this on VSCode Insiders 1.53, was able to set using ~:
{
"php-cs-fixer.executablePathWindows": "~\\AppData\\Roaming\\Composer\\vendor\\bin\\php-cs-fixer.bat"
}
Seems that the ~ is transformed to match C:\Users\[you].
I know for sure that ${env:APPDATA} works because I use it in the setting : "emmet.extensionsPath": "${env:APPDATA}\\Code\\User\\Emmet Settings",
Check this documentation section. Unfortunately, this issue complains that it is not supported in every settings and extensions. I strongly suggest that every one upvote this issue so we have better chance MS takes care of it.

VSCode: 3 dots popping up and disappearing in editor

I have VSCode installed with
Version: 1.52.0-insider (user setup)
Commit: 0a80aacc7be1ab03ec0f94b8ac1a84949a83f35d
Date: 2020-11-26T07:36:22.965Z
Electron: 11.0.2
Chrome: 87.0.4280.63
Node.js: 12.18.3
V8: 8.7.220.24-electron.0
OS: Windows_NT x64 10.0.19042
I also installed C/C++ for Visual Studio Code 1.1.2.
Then created some hpp file.
Also when hitting enter on some random line, 3 dots appear on some strange empty lines.
After 2 seconds these dots and lines disappear again.
This makes working in the editor really hard when lines come and go.
Here is a screenshot:
Any idea how to disable these popping up dots?
This was happening to me because of the GitLens extension. I uninstalled it and now the issue is gone. It seems they have open issues for this issue but they are not addressed (as of today)
https://github.com/microsoft/vscode/issues/111472
https://github.com/gitkraken/vscode-gitlens/issues/1312

How can I get Visual Studio Code autosave working again?

The Visual Studio Code setting "files.autoSave": "onWindowChange" has stopped working for me. It has worked properly for me every day in the past year. (I'm wondering if it may possibly be related to either my most recent update to Catalina or the most recent update to VS Code.) I have the files.autoSave setting only in this file: ~/Library/Application Support/Code/User/settings.json.
Does anyone have suggestions on how I can get the autosave feature in vscode working again?
Visual Studio Code 1.49.0
Commit: e790b931385d72cf5669fcefc51cdf65990efa5d
Date: 2020-09-10T17:39:53.251Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.6.0 - macOS Catalina 10.15.6
i personally don't like to use autosave on window change. I use "files.autoSave": "afterDelay" and set the delay files.autoSaveDelay": 500 here. Why I used this over the autosave window change is because it's much faster and automatically done every 500ms!
I was using Witch by Many Tricks, https://manytricks.com/witch/. After updating MacOs to Catalina 10.15.6, I believe that Which may have been interfering with VS Code ability receive window focus callbacks (I'm guessing). When I disabled Which, all is fine now. Thank you.

What did I break, VS Code now complains about Readme markdown generated by Azure Devops

Not sure what I did, but I mist have broke something. I was using the MSSQL extension to query sql and the next thing I know Im getting complaints about a readme file I added when I setup the repo for my project. dotnet build still succeeds, but I dont recall seeing these messages when I first started the project, nor the red squiggles in the file itself.
Version: 1.39.1 (system setup)
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17134