Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runme vscode extension, on WSL2 run code in CMD.exe instead of WSL #657

Open
wasdee opened this issue Aug 21, 2024 · 3 comments
Open

runme vscode extension, on WSL2 run code in CMD.exe instead of WSL #657

wasdee opened this issue Aug 21, 2024 · 3 comments
Assignees

Comments

@wasdee
Copy link

wasdee commented Aug 21, 2024

error log


> web@0.0.1 dev
> vite dev

'\\wsl.localhost\Ubuntu-24.04\home\ben\xxx'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported.  Defaulting to Windows directory.
'vite' is not recognized as an internal or external command,
operable program or batch file.

reproduce

  1. enter vscode connect to WSL
  2. run a readme cell

connect to WSL

@sourishkrout
Copy link
Member

Hi, @wasdee, are you sure cmd.exe isn't the default shell profile selected in VS Code? Runme does not influence this selection, and I'm unsure if WSL filters out all invalid shells.

@sourishkrout sourishkrout self-assigned this Aug 21, 2024
@wasdee
Copy link
Author

wasdee commented Sep 8, 2024

It might be on windows. But, bash is my wsl shell

@sourishkrout
Copy link
Member

It might be on windows. But, bash is my wsl shell

Makes sense. We're about to release a warning notification to let users know when their environment is incompatible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants