I am developer behind a more clean Monokai Theme on VScode. [It is more of a simple hack.]
https://marketplace.visualstudio.com/items?itemName=Mit.Monokai-Polished
Whenever I release a minor update VScode doesn't delete older version from /extensions folder after reloading the window. How do I remove this bug.
My source code is for extension is available at this repo.
The older version will not be deleted if you just reload VSCode (clicking the Reload button in Extensions tab or using the Reload Window command. In order to really delete the older version, you need to Restart VSCode (close and reopen, all instances).
By the way, it appears to be designed this way, and not a bug. (related issue in VSCode repo).
Related
GitHub Copilot stopped working after it asked to restart vscode for the last update I installed, right now it doesn't even show the icon and there are no suggestions either, it's as if it wasn't installed.
I unistalled everything, even the vscode itself, deleting all the files and configuringicon in case there was a conflict or error, but the extension still does not work.
If anyone knows how to fix it or what is causing the error, I would be very grateful.
Rolling back to the previous version (1.63.7601) fixed it for me.
Click on extensions icon on left menu bar
Search for Copilot
Click the settings cog > Install another version
Select 1.63.7601
Reload VSCode
Whenever I update my VSCode, few of my extensions gets inactive automatically. It's get activated if I uninstall the extension and reinstall it. you can find in the screen shot that few are inactive.
Very likely those extensions are outdated and are known to have compatibility problems with the current vscode version. Try updating those extension to their latest version.
Also check if you use the latest vscode version.
I can't open a new external terminal with CTRL + SHIFT+C. Did a new update remove this function? I was able to use this shortcut before, but now I cannot.
This appears to be a bug with the current version of Visual Studio Code, as multiple users are reporting it isn't working across different operating systems:
GitHub Issue #1
GitHub Issue #2
I updated to 1.57 the other day, and it is not working for me now either. Previously it was on a slightly older version that I updated from.
Update:
The latest Visual Studio Code Insiders release (1.58) has addressed this as noted in this GitHub issue. If you really want this functionality back, you can download the Insiders edition, otherwise you'll need to wait until the next update for the main application.
Final Update:
The May Recovery update resolved this issue. Download the update, and you should be able to once again open external terminals through the command.
It was the issue vscode 1.57 which lasted for about an week.
If you upgrade to the latest version of vscode, it will work now.
Good Job VSCODE !
So with the new VSCode update version 1.14.0 it causes major issues which are
High CPU usage (causes freezes)
random crashes
extensions are not availabe
IntelliSense working half of the time
So my question is how can I roll VSCode back to the previous version without losing my configurations?
After 1.14.0 I have the same issues, specifically freezing for multiple seconds randomly during intellisense. They label it the previous month, so 1.14.0 is the "June" release.
Going to https://code.visualstudio.com/updates/v1_13 and click the links right below the title to download the older versions (don't click the green download button).
Downloading that windows executable for 1.13.1 and running it installed the old version over the new version without issue. All of my settings are the same and everything works fine.
Update April 2021
To find the previous version, click the Updates link on the top nav
Then click the correct link for your platform - that will download the latest update for that version.
Note:
After downloading the previous version (1.54.3 system) and reinstalling overtop the current (more recent) version, I received an error from the Python extension:
Cannot activate the Python extension because it depends on the Jupyter extension, which is not loaded.
Somehow the Jupyter extension was damaged and it was necessary to reinstall the Jupyter extension (that extension was greyed-out in the Extensions pane - it was only necessary to click the gear icon beside the Jupyter extension and install the latest version). After that, everything worked.
So, not completely painless, but it was easily resolved.
Working with Visual Studio Code I have noticed if a file you are working with change, whenever that file get focused in a code panel it will be reloaded from the disk (if you don't have changes in the file through VSCode).
However, if you are on that file there is no alert to warning you about file changes.
I've been reviewing the settings and I cannot find anything like the visual studio option:
Detect when file is changed outside the environment
So my question: Is there any hidden setting or some hack to make that warning happen.
Update
Solved in version 0.3.0 of Visual Studio Code.
The file will be updated from disk if there is no changes through the editor. (very useful to read log files during a process execution)
If there are changes on both sides (from disk and through the editor) when ever you try to save the file using VSCode, the editor will warn you about that situation (i.e. "dirty writes") and a file comparison will allow you to decide what to do.
VSCode will never refresh the file if you have changes in that file that are not saved to disk. However, if the file is open and does not have changes, it will replace with the changes on disk, that is true.
There is currently no way to disable this behaviour.
{
"files.useExperimentalFileWatcher" : true
}
in Code -> Preferences -> Settings
Tested with Visual Studio Code Version 1.26.1 on mac and win
SUPER-SHIFT-p > File: Revert File is the only way
(where SUPER is Command on Mac and Ctrl on PC)
In version 1.57.1 (June 2021) there is still no setting like Detect when file is changed outside the environment.
But if the file was accidentally changed outside, you can easily revert the changes with just the Undo (Ctrl+Z) command
On Ubuntu, after creating a new file using vscode, it doesn't show up until I refresh the explorer manually. It's really frustrating. There was a key I changed in settings.json and everything worked fine after that:
"files.legacyWatcher": "on",
save, restart the vscode and be safe :)