How to stop terminal rotating icon in VSC - visual-studio-code

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.

Related

How to toggle all breakpoints in VS Code?

I am looking for a way to assign a keyboard shortcut that would toggle all breakpoints in VS Code.
The same key should either disable them all or enable them all back, i.e. it is not about only disabling or only enabling them via two different shortcuts.
I cannot find any action responsible for that. There are only disableAllBreakpoints, enableAllBreakpoints, removeAllBreakpoints and reapplyBreakpointsAction.
The last one sounds somewhat promising but I am not sure if this is the one that I am looking for? It does not toggle them so perhaps this is not it?
Essentially, I am looking for a toggleAllBreakpoints but I am not sure if it exists.
My VS Code version is:
Version: 1.63.0
Commit: 7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
Actually, I have found it already - that can be achieved with toggleBreakpointsActivatedAction.

Syntax errors, but no errors and code runs

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

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.

VS Code: select file, press delete - instead of deleting file it tries to regex-find file called 'Delete'

In VS Code I select my file in the Explorer tab:
After I press Delete button, instead of deleting VSCode starts file search:
If I press delete multiple times it just keeps doing its thing:
It looks like a bug but maybe there is a secret shortcut to turn file search mode on/off that I don't know. Is there?
I'm on Ubuntu x64 with VSCode:
Version: 1.36.0
Commit: 0f3794b38477eea13fb47fbe15a42798e6129338
Date: 2019-07-03T13:20:56.241Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.18.0-25-generic
EDIT: please ignore my terrible terrible praxis of deleting spec files
Update:
Microsoft fixed it in last update
Original answer:
This is a known issue from last patch, it's going to be fixed in the next update.
Check this:
https://github.com/microsoft/vscode/issues/76514
Workaround:
https://github.com/microsoft/vscode/issues/76514#issuecomment-508841597