Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
VS Code reloading to change icons
See original GitHub issue- I’m sure this issue is not a duplicate?
I’m assuming the current icon manifest approach of handling presets forces VS Code to be reloaded in order to update the icons.
Could this be avoided if instead the different presets were abstracted into their own extensions, and vscode-icons refactored so that it’s only in charge of handling project detection and theme switching?
I’m asking this because I can very easily go to settings.json, change workbench.iconTheme and immediately see the icons updated, without having to restart VS Code.
So, this extension would only have to set:
"workbench.iconTheme": "vscode-icons", or "workbench.iconTheme": "vscode-icons-angular", etc. accordingly.
Issue Analytics
- State:
- Created 6 years ago
- Comments:24 (23 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@MonsieurMan It’s time to invest in an SSD. Development on HDD is a PITA.
From some testing I’ve done, unfortunately,
vscodeloads the manifest file before it invokesactivate. So any manipulation before callingactivateis not possible. This means that in case the user has set custom iconsvscodewill have to restart anyways (even if we use two manifest files).