I have been using VSCode for years and never seen this before.
https://i.imgur.com/wie0kAu.png
I've tried uninstalling and re-installing, but the problem persists.
Before I re-installed I deleted every code folder I could find in my AppData folders, but when I re-installed all my extensions etc came back straight away, so I think I might have missed a folder somewhere.
Can someone point me to where I should look to nuke all traces of VSCode so I can re-install it, not sign in with sync and start completely fresh.
Just in case someone finds this in the future, I had installed a tweaker for Windows called Windhawk which can let you tweak things, one of the things you can tweak is VSCode. Seems like I enabled that tweak and by default it changes the interface font to Comic Sans. 🤦♂️
https://i.imgur.com/LIBvhW6.png
Related
Typing in the integrated terminal in VS Code on Big Sur is very annoyingly laggy and slow. This is the only application that experiences this, iTerm, etc. do not experience this issue. I tried disabling all plug-ins, themes, fonts, etc. to try to get to root cause.
Based on the thread here I was able to successfully mitigate the issue by running this command: codesign --remove-signature /Applications/Visual\ Studio\ Code.app/Contents/Frameworks/Code\ Helper\ \(Renderer\).app and restarting VS Code, the lag is completely gone and everything is back to normal.
If you trust VS Code developer then removing the signature should not be an issue but YMMV.
For me, I was super happy to find this solution, as it was driving me crazy.
Probably an update on Konstantin Popovskikh's answer that was deleted.
In settings.json, setting this:
"terminal.integrated.gpuAcceleration": "off",
Helped a lot for me, however it does have the side effect of not rendering underscores while typing - but for me, this is the lesser of two evils.
Note: You don't appear to have to reload the session you can just save the .json file and the terminal will update (you can visibly see it change slightly).
Overnight, any help I had for Unity3D in VSCode, i.e. intellisense, disappeared. And I get the sense, no pun intended, that I'm not the only one who's afflicted.
I've tried updating and reinstalling what I assumed VSCode needed to make Unity3D intellisense work. And have checked and re-checked settings, reinstalled VSCode package, in Unity3D.
I've worked through a few tutorials that claimed to address the issue.
What else does VSCode depend on to make this relationship work?
Thanks! Here's to hoping you've fixed this and your life has gotten easier!
Try going to Edit > Preferences > External Tools > Regenerate Project Files (This is because of a bug where the VS Code extension doesn't generate the project files correctly the first time, you can check it out here).
You'll need to be using the VS Code Editor Extension 1.2.0 (you can check which version you're using in the package manager) or later for that option to appear. Also if for whatever reason there are 2 .sln files in your project folder (I've had that happen before, though it's less likely), that also causes problems.
Ok. First, thanks to Lightning_A and Charleh!
The resolution to my specific circumstance was to install the VSCode extension "Unity Snippets Modified" https://github.com/with-heart/vscode-unity-snippets
I had been using https://github.com/kleber-swf/vscode-unity-code-snippets.
Perhaps it's just a matter of Kleber's extension, which is/was great, was broken upon updating Unity to 2020? I dunno and don't have the time to look into it, unfortunately.
Hopefully, my question, the answers I received, and my subsequent resolution saves others from the rabbit-hole I went down.
Again, thanks everyone!
I need to figure out how to turn off emphasized items in Visual Studio Code
This might sound like a strange requirement, but in my workflow vscode functions as less an IDE than a cross-platform ViM-esque frontend with lots of remote development tools built-in.
Due to this use case, I don't need or want the linting features to show up in the file browser. How might I accomplish this?
Attempts to solve the problem
I've run out of search terms here and cannot find an answer.
Searches including terms in this question's title yielded little
SO-specific search queries also yielded little
This seems to be somewhat related, at least as a representation of the "feature" I'm referencing: VS code containes emphasized items but no error
VSCode "preferences" do not appear to show what I'm looking for, likely an issue with me not searching for the right variable name.
In my experience with VSCode it has been wonderfully customize-able, so I'm guessing there's a setting somewhere ready to be modified to accomplish this. Any help much appreciated, thanks!
My use case was a bit different: after viewing some files in a git submodule those files became linted, and errors and warnings cluttered up my VS Code Explorer file browser window on files I had no intention of ever handling. I basically wanted a way to clear out those lint warnings, and found it here. The solution is to reload the window:
CtrlShiftP on Windows/Linux, ⌘ShiftP on Mac -- then select "Developer: Reload Window"
One by-product of reloading the window is that it clears out those unwanted warnings (at least until the next time I visit the file). It also has the effect of clearing out warnings on files that I would normally want to see, of course, but chances are I'll be visiting those files again soon, so it's fine. Not a perfect solution, but it works for me and my use-case; hopefully it can help others.
I don't know how to turn it off, but I had this on multiple folders and I fixed it by renaming the folder to a random name, then naming it back to the name it was before and the error would go away.
If you have this issuse then uninstall extention then CtrlShiftP on Windows/Linux, ⌘ShiftP on Mac -- then select "Developer: Reload Window" then type developer: relode page this issuse automatically resovle
i have this issuse then i uninstall extension then this issuse resolve.
I was able to permanently prevent this by adding the files to the .gitignore file. It seems that this happens in a cloned repository when you add new files.
In XPages, when I try to open a .js or .jss file, I often get just the tab wirh "Client/Server JS Editor" and nothing else, i.e. the file doesn't load. From the Navigator Eclipse view, I can open the same .js or .jss file using any other editor without problems. And then, it sometimes works, but I don't know yet when it does and when it doesn't. The other Editors are okay by the way, .lss opens nicely.
This behaviour I get for a few weeks now. Since it started I reinstalled Notes a few times, I upgraded to FP8, I also reinstalled Windows10 and Windows10 upgraded me to the Creators Update (with the fix, in the end). There's nothing that explains to me why the file doesn't show up on the screen.
Anyone familiar with this? Could you please tell me how to repair this?
Thanks!!
It's a bug introduced with FP8 that is fixed in FP8 Interim Fix 1. See this document for download options for FP8 IF1.
As a workaround you can do a clean/rebuild of the nsf and then use the SSJS editor.
Using Visual Studio Code I have installed a few extensions (like Guidelines showing vertical dotted lines between pairs of matching brackets). When I start VS Code I can see all my extensions working fine in the Editor window.
However, when I switch to another tab within VS Code, I no longer see the Guidelines or evidence of any extension working in the new editor tab. Worst of all, when I then switch back to my original tab, all the guidelines etc that were there a few seconds ago are gone!
To fix the issue I have to restart VS Code. This can't be right! Has anyone hit the same problem?
I have tried uninstalling VS Code where it warns me some components could not be uninstalled and I have to do them manually. It doesn't tell me which. When I then reinstall, the extensions are visible (without me reinstalling them) but again I hit the same issues as above.
Please help?
Seems like having too many extensions installed, or perhaps one that is misbehaving behind the scenes, causes this problem. Reduce the number of installed extensions. Use Help->Developer Tools -> Console to see if there are any messages relating to the Extensions server