Open PurtucRobert opened 1 year ago
@PurtucRobert I'm using VSCode v1.74.2 and the workaround for this as far as I can tell is by turning off sandbox mode in your vscode settings as it apparently messes with the entire extension, if you don't know how to disable it
go to Settings > Search "Sandbox" and then uncheck it and restart vscode afterwards if it's still persistent then i'm not too sure what else you can do hope this helps
I was able to get it working, for anyone with my scenario, maybe this can help. I develop on windows, using vscode, inside of wsl. I had to enable the glow with a vscode window pointed at my windows file system, then the next time I opened a window in WSL, it was working for me
Still hitting this problem on VSCode 1.74.3 with the 12/9/2022
release of this extension.
Giving appropriate permissions to workbench/ seems to fix it.
sudo chown -R $(whoami) /Applications/Visual\ Studio\ Code.app/Contents/Resources/app/out/vs/code/electron-sandbox/workbench/
After updating the VSCode to the latest version(1.74.1) the glow is not working anymore