{"id":2107,"date":"2022-08-22T17:42:37","date_gmt":"2022-08-22T15:42:37","guid":{"rendered":"https:\/\/nguenkam.com\/blog\/?p=2107"},"modified":"2022-08-22T17:42:37","modified_gmt":"2022-08-22T15:42:37","slug":"how-to-open-vscode-from-a-windows-linux-subsystem","status":"publish","type":"post","link":"https:\/\/nguenkam.com\/blog\/index.php\/2022\/08\/22\/how-to-open-vscode-from-a-windows-linux-subsystem\/","title":{"rendered":"How to open VSCode from a Windows Linux Subsystem"},"content":{"rendered":"\n

Issue :<\/strong> When typing “code .”<\/span> command on WSL , we get the following error-message : “Command ‘code’ not found” <\/span>. <\/em><\/p>\n\n\n\n

<\/p>\n\n\n\n

SOLUTION 1<\/h4>\n\n\n\n

Assuming you have installed VSCode in its default place, then in WSL you can do :<\/p>\n\n\n\n

PATH=\"$PATH:\/mnt\/c\/Users\/your-user-name\/AppData\/Local\/Programs\/Microsoft VS Code\"<\/code><\/pre>\n\n\n\n
and run\u00a0code.exe .<\/code><\/p>\n\n\n\n
<\/p>\n\n\n\n
SOLUTION 2<\/h4>\n\n\n\n
PS:  First, try installing the\u00a0Remote - WSL<\/code>\u00a0extension in VSCode (or the meta\u00a0Remote Development<\/strong><\/code>\u00a0extension pack, which includes the WSL work).<\/em>  (Not sure that\u00b4s is the main problem, but it could help<\/em>.<\/span>)<\/p>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n
try running\u00a0code .<\/span><\/code>\u00a0under PowerShell <\/strong>– Does that work? If not, then VSCode <\/strong>isn’t in the Windows path<\/strong>. Try reinstalling it — If it’s not in the path, some other associations may not be correctly installed either. I don’t recall if there’s an option during installation to add or not add it to the Windows path, but if so, it could be that it was deselected during installation.<\/p>\n\n\n\n
If it does launch in Windows, then obviously it’s in the Windows path. By default, WSL appends the Windows path to the default path in Ubuntu during init. So (again, by default)\u00a0code .<\/code><\/span>\u00a0should work in WSL<\/span> if it is working under PowerShell.<\/span><\/em><\/p>\n\n\n\n
Check your\u00a0$PATH<\/code>\u00a0under Ubuntu (echo $PATH<\/code>). Is the …\/Microsoft VS Code\/bin<\/code><\/strong><\/em>\u00a0directory<\/span> (wherever it is installed) in the path? If not, then WSL may not be doing its default append. Edit\u00a0\/etc\/wsl.conf<\/code><\/a>\u00a0under Ubuntu and look to see if there’s an\u00a0[interop]<\/code>\u00a0section, as in:<\/p>\n\n\n\n
[interop]\r\nappendWindowsPath=false<\/code><\/pre>\n\n\n\n
If so, then change it to\u00a0true<\/code>\u00a0(or, delete it entirely) to allow WSL to add the Windows path. While it’s the default setting if missing, you might try adding it and setting it to\u00a0true<\/code>\u00a0(although that shouldn’t have any effect).<\/p>\n\n\n\n
If that still doesn’t work, then check your startup scripts (e.g.\u00a0.profile<\/code>,\u00a0.bash_profile<\/code>,\u00a0.bashrc<\/code>) to see if there are any modifications to the\u00a0PATH<\/code>\u00a0which could be causing this problem.<\/p>\n","protected":false},"excerpt":{"rendered":"
Issue : When typing “code .” command on WSL , we get the following error-message : “Command ‘code’ not found” . SOLUTION 1 Assuming you have installed VSCode in its default place, then in WSL you can do : and run\u00a0code.exe . SOLUTION 2 PS: First, try installing the\u00a0Remote – WSL\u00a0extension in VSCode (or the […]<\/p>\n","protected":false},"author":1,"featured_media":1721,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[250,193,140,502,161,217,571,299,501],"_links":{"self":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2107"}],"collection":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=2107"}],"version-history":[{"count":1,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2107\/revisions"}],"predecessor-version":[{"id":2109,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/2107\/revisions\/2109"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/media\/1721"}],"wp:attachment":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=2107"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=2107"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=2107"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}