Recently changed all my view files from .jade to .pug on my Node app. But when I open the files in Visual Studio code, they are not hightlighted, does VS Code not have syntax highlighting for .pug file?
I stumbled across the same problem. For me the problem only exists when I have the Preview extension installed. Disabling this extension has solved the problem for me.
I've opened an issue to the VS Code Repository:
https://github.com/Microsoft/vscode/issues/44713
Are you sure that you have the latest version of Visual Studio Code installed? Mine (v1.18.1) came with .pug support preinstalled, and highlights Pug files without a problem. The Wikipedia page also says that Pug syntax highlighting support is present in VS Code.
Related
I have the latest Visual Studio Code.
I have installed the latest SuiteCloud Extension for VS Code.
There is no intellisense.
I have also installed the SuiteNippets extension -- which is ok--but not full intellisense.
I am baffled as to why this is missing. Do I need to import/reference something from NetSuite--despite using their extension already?
How do I enable intellisense in VS Code for SuiteScript?
See my previous answer to a similar question. It's possible to use the Head-in-the-Cloud bundle to create javascript transpiled from TypeScript files. The code completion is good and you have the added benefit of type checking.
I'm developing an extension for Visual Studio Code for the proprietary language that the product I code for uses because I hate the antiquated IDE ships with it. Everything is going fine except for one issue. When I close and open Visual Studio Code, Visual Studio Code seems to "forget" my extension. Syntax highlighting, code completion, commands that I've implemented all stop working. I have to disable and then enable to extension for it to start working again. I am OK with this for personal use. However, I want to push this out to other users both in and outside of the company. If any code would be helpful, let me know, and I will happily provide it.
I resolved this issue. It was because in my settings.json for VS Code I had an entry for the file extension pointing to an extension that I had removed. Removing that line from my settings.json resolved the issue of things not working when I opened VS Code.
Thanks to everybody for their comments.
The issue is VS code doesn't see UnityEngine.UI library.
I had this issue before and I solved like it this:
I changed the code editor in preferences to Visual Studio, regenerated files and launched c# project. On the start, vs created needed .csproj files and then I closed vs and changed it back to vs code and it workeed.
However, now I am working on another project and I encountered same issue, I tried the method I described above but it didn't work.
Any ideas?
So, after days of tinkering and trying different solutions I found on the internet I finally found out how to solve it (all by myself).
Switch to VS and make sure it detects the UnityEngine.UI library. Then don't close VS, switch to VS Code, don't hit "regenerate files", launch c# project, enjoy!
These steps covered several possible issues:
https://stackoverflow.com/a/70977258/6046022
(just an overview, follow the link for the complete steps)
downgrade VSC package
re-install Unity UI
regenerate files
I am using Visual Studio Code for the front end development project. Unfortunately, VS Code stopped showing me colored version of SASS file. May I ask please what is the solution?
I've had the same problem, you can install this extension in vscode:
https://marketplace.visualstudio.com/items?itemName=Syler.sass-indented
When I start Visual Studio Code (Win10[64bit]), click on extensions overview, all my extensions disappeared. The overview is empty. I also can't load any new ones. But I think all the extensions seem to work.
In Addition there is a clock on the extensions symbol and it seems "loading", but nothing happens. Waiting a long time or restart didn't improve anything.
This is my first question, thanks for help.
As commented by the OP above:
Thanks for your ideas, I re-installed and everything is fine now.
The hint came from Maja Okholm:
perhaps try to repair the installation of visual studio code? Control panel > programs > programs and features, find visual studio code and click repair