-
-
Notifications
You must be signed in to change notification settings - Fork 862
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
Unable to mux into WSL from windows, wezterm-mux-server seems to ignore all config options #604
Comments
inside wsl, please run:
and attach |
I've added the server.txt file. |
Your wsl config is missing a |
If you're using wsl2, then I don't think this will work using unix domain sockets: microsoft/WSL#5961 |
Please confirm whether you're running WSL 1 or WSL 2; WSL 2 doesn't currently support unix domain socket interop. |
This issue has been automatically closed because there has been no response to the request for more information from the original author. With only the information that is currently in the issue, there isn't enough information to take further action. Please reach out if you have or find the answers we need so that we can investigate further. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Describe the bug
No matter the combination of commandline flags and config files, the wezterm-mux-server always starts its socket at
~/.local/share/wezterm/sock
.Environment (please complete the following information):
wezterm 20210314-114017-04b7cedd-120-g217dbfb9
To Reproduce
Steps to reproduce the behavior.
Follow the docs on https://wezfurlong.org/wezterm/multiplexing.html#connecting-into-windows-subsystem-for-linux
Configuration
wsl config
windows side config:
Expected behavior
Expect to get a wezterm window with a shell of my wsl debian install.
Screenshots
The text was updated successfully, but these errors were encountered: