-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
WSL2 support for inspector #355
Comments
vite uses You may be able to set the vscode executable in the Regarding key-combo, i'm a bit confused, ctrl-shift worked when i used it in a virtual machine (i don't have a native windows installation). Please try other combos to see if any of them work. eg Note it is not recommended to use printable letters together with |
please let us know if EDITOR helps with your issue and if there is a key-combo that works for you. |
Going to close this here, please follow the upstream issue for picking a more suitable editor in WSL yyx990803/launch-editor#16 Feedback regarding the keycombo is also still welcome though in my testing ctrl-shift did work fine in my windows vm and given you can configure any other combo of your chosing to work around local collisions there's little more v-p-s could do to improve the situation |
Describe the problem
When using this with Windows 10/11 + WSL2, there are two issues:
vim
window in the SSH console. It also doesn't respond correctly to keypresses so you can't exit vim. 🙀ctrl-shift
seems to work. Only settingshowToggleButton: 'always'
works.Describe the proposed solution
Perhaps there is some way for the plugin to understand that it's running in WSL2 + VSCode and send a message to the VS Code process?
Reproduction
Alternatives considered
Importance
nice to have
The text was updated successfully, but these errors were encountered: