Tools: Mystery Resolved: Switching Repeatedly from WSL to PS - Issues
Source: Dev.to
After having previously built an Ubuntu server, I am a little bit more fond of using WSL instead of PS in Windows. Feeling like I am "getting by with something" using linux commands on a windows pc. It's a nice little feature. But, I ask, what is all of that power good for if you are repeatedly running into super annoying unresolvable permission issues? I have gotten around this somehow until I started using antigravity. Being excited, I installed the new IDE and decided I was gonna do my linux nonsense on there too. The annoying mount issue rears its head, of course. (Yes I know wizard, should have been a read flag) I proceeded to try to use it anyway. No one is exactly over hear showing me how to stay out of messes. I misuse things, fall on my face, and share it so you don't have the same issue. Grit is one of my superpowers. Fast forward through over two years of coding like this, and having gotten around it by using things like codespaces or running everything sudo. (Yes I know, I'm banned) XD The fix: literally 5 minutes of reading. I should have delt with this before. I simply had to properly mount WSL before entering my code editor. All I had to do was open a terminal, switch to WSL in said terminal, and type 'code .' This opens your code editor with your projects mounted properly, resolving all permission issues and "things not installed" issues. What it should NOT look like when you start: What it SHOULD look like: Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse