To have a good look of vs code I have downloaded the extension called "Vibrancy".
It is really reallu buggy extension I have ever downloaded. Even after uninstalling, it keeps on showing its effect.
.
To delete it permanently (in windows)
Close all tabs and windows.
press win+R
Type:- Temp and new screen pops up. Here delete all files.
After this again press win+R.
Type:- %temp%. And also delete all files.
Also Restart vs code few times
Related
I encounter the "Save" and "Save As" menu items greyed out randomly and regularly while editing files in VS Code. Been happening for a few years. Most of the time it's while I'm editing Golang code but it has happened for other file types. If I click on the x to the right of the file name tab for the open file, I then get the option to save the file. Ditto if I try and close VS Code.
So VS Code knows there are unsaved changes. Closing VS Code completely and restarting it "fixes" the issue until the next time. Did a search and I don't see any "recent" issues like this that others have experienced. Running on macOS. Happened under Big Sur, Monterey and now on Ventura. Currently running VS Code 1.72.2. I tried to narrow it down by disabling some extensions but it still happens.
Tried removing extensions. Still happens. Uninstalled and re-installed VS Code.
I have been using visual studio code for about a year now. Recently I went to save one of my files and visual studio code gave me the error message this file conflict with a previous version. I clicked on the error and it presented me with a screen show the differences. I turned out I had added a line at the top importing defining a new constant. When I clicked override visual studio code presented me with a blank file. I went to look at my files and found that every file I have every worked on in the program has been changed to a blank file. Now whenever I try to save a file nothing happens, and I can't close tabs. I use a macbook if that helps in any way. Does anyone know how I could retrieve my files and how to prevent this prom happening again.
Edit: this applies to all my files not just ones associated with this project.
I switched from notepad++ to visual studio code but notepad++ had an interesting feature which was to reload the file
In this way the changes with control z and control y were eliminated.
And you started the editor again from 0.
It was very useful to me.
Now in visual studio code there is no option.
How could I get it?
Edited I found a way to do it but it has a problem.
Edit this shortcut by removing the developer option from it.
But the problem is that if you have multiple files it updates them all.
What you want is for it to reload only the file you have open in the foreground.
Same thing notepad++ does when you hit the reload from disk button.
I am trying to navigate to the explorer window via Ctrl+Shift+e but this sequence of keystrokes is not recognizable by VSCode 1.55.2.
I checked this two ways. First, via trying to check what Ctrl+Shift+w and Ctrl+Shift+e were binded to via keyboard shortcuts (Ctrlk, Ctrls) and then recording the keystrokes to reveal what they were binded to.
You will observe that ctrl+shift+w is recognized. Then, in the gif, when I press ctrl+shift+e it renders as ctrl+shift+unknown.
Then, whenever in a saved open file in the editor, when I press ctrl+shift+e hoping that the explorer navigator opens up on the left, that does not happen. Instead the file becomes unsaved with an underscore e appearing in the file.
This is completely new and strange behavior of the editor. I did not encounter this before.
Any help is appreciated.
Edited to add update: VSCode folks indicate that this is a known issue. Ctrl+shift+e translates into insertion of an emoji, it seems. See their comment here.
Same thing happened to me, using linux (ubuntu).
I installed it from the snap store, and tried reinstalling from there and the problem was still there.
Uninstalled and installed it manually from de .deb package at their webpage and it was solved.
Maybe it's an issue they have solved in the latest version (1.15.8) but it's still unsolved in the snap version (1.15.2 in your case, i didn't pay attention on what was my version).
Same problem. Installing vscode from .tar.gz - works perfectly fine, installing from snap leads to unexpected behaviour on Ctrl+Shift+E
I am working on a .Net Core application and I keep running into this problem where I get all sorts of random issues appearing in the Problems window in VSCode for "__virtual" files. There are no problems in the actual razor page (.cshtml) and everything is working how we would expect. Is there a way in VSCode to mass ignore all problems from __virtual files?
This started to happen to me after the latest update of Visual Studio Code.
My solution was to configure file association for .razor__virtual.html files into text
Open visual studio code
Click Settings icon in the left bottom and click Settings
In the search box, search for Files: Associations (Copy-paste this)
Click [Add Item] button and enter **/*.razor__virtual.html for key, text for value.
It should look like this,
Done!