Use as remote VS Code server extension in WSL2

robb0wen / synthwave-vscode

Synthwave inspired colour theme for VS Code 🌅🕶

MIT License

5.16k stars 1.18k forks source link

Use as remote VS Code server extension in WSL2 #176

Open blooddrunk opened 4 years ago

blooddrunk commented 4 years ago

Not sure if this is the right place to ask, but I can't find instructions about the question. My workplace sits in the home directory of WSL distro, and I'm using Remote - WSL to access it(from VS Code Insiders installed in Windows host ran as Administrator of course). This way the theme cannot be enabled(admin privilege error popped up). It's happening since I migrated from WSL1 to WSL2 and move my workplace from Windows host to remote WSL(https://github.com/microsoft/WSL/issues/4417#issuecomment-540676694). I had to install synthwave again as a remote VS Code Server extension. I not sure how to toggle with the Admin Privileges thing since I'm running VS Code in Windows and install the extension in remote WSL distro. Any ideas? Thanks in advance!

PrimerFender commented 4 years ago

In my experience the extension installs fine/normally when launched from workspace in WSL2, but am unable to enable text glow effect (> Enable Neon Dreams) and results in the admin message. I know the extension needs write permission to overwrite some core VS Code files to add the glowing text effect, but not sure which ones, or if it supports those provided by WSL Remote. @blooddrunk Do you mean you cannot install the extension at all, or just enable the text effect?

blooddrunk commented 4 years ago

The extension can be installed(I can see it in ~/.vscode-server(-insiders)/extensions). It just keeps warning me with You must run VS code with admin priviliges in order to enable Neon Dreams. when I'm trying to enable the glow effect.

PrimerFender commented 4 years ago

@blooddrunk I was able to get it working by enabling Neon Dreams normally first. I think I just opened a workspace in an empty folder on my desktop, went through the normal process (Run as Administrator, Enable Neon Dreams, restart VS Code). Then opened a folder in WSL2 and it still works. From a directory in WSL2 I can type code . and it opens.

blooddrunk commented 4 years ago

@PrimerFender Thanks a lot! I can confirm this workaround works!

bonellia commented 2 years ago

Just letting you know, it works in Windows 11 as well. However, it will trigger a warning about VSCode installation being corrupt which I think is ignorable given that the relevant files are modified intentionally.