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

Windows unix domains don't support separate sockets #5140

Open
cprusprus opened this issue Mar 10, 2024 · 2 comments
Open

Windows unix domains don't support separate sockets #5140

cprusprus opened this issue Mar 10, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@cprusprus
Copy link

What Operating System(s) are you seeing this problem on?

Windows

Which Wayland compositor or X11 Window manager(s) are you using?

No response

WezTerm version

20240226-174525-22424c32

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

I have 2 different unix_domains each with different socket_paths. However, they both connect to the same domain (same windows, tabs, panes). It would be nice to be able to have multiple unix domains to organize work (each domain/project would have separate workspaces).

The bug is weird since WSL is apparently also a unix domain, but that is treated as a separate domain from the main unix domain and can be multiplexed independently.

To Reproduce

C:\wezterm\target\release\wezterm.exe connect unix
Setup tabs and splits
C:\wezterm\target\release\wezterm.exe connect unix2
This opens the same tabs and splits as unix had. In fact, activating tabs activates the tab in the other WezTerm instance.

Configuration

config.unix_domains = {
{ name = "unix", socket_path = os.getenv("USERPROFILE") .. "\.local/share/wezterm\sock", },
{ name = "unix2", socket_path = os.getenv("USERPROFILE") .. "\.local/share/wezterm\sock2", },
}

Expected Behavior

C:\wezterm\target\release\wezterm.exe connect unix2 would create or connect to an entirely different domain like the docs say, with each domain using a different socket pair.

Logs

C:> C:\wezterm\target\release\wezterm.exe connect unix
23:38:21.665 INFO mux > detaching domain
23:38:21.666 INFO wezterm_client::domain > detached domain 1
23:38:21.666 INFO mux > domain detached panes: [5, 2, 3, 4, 1]
23:38:21.668 INFO wezterm_client::domain > detached domain 1
23:38:21.669 INFO mux > domain detached panes: []
C:\ > C:\wezterm\target\release\wezterm.exe connect unix2
23:39:19.750 INFO mux > detaching domain
23:39:19.752 INFO wezterm_client::domain > detached domain 2
23:39:19.754 INFO mux > domain detached panes: [1, 2, 3, 4, 5]
23:39:19.755 INFO wezterm_client::domain > detached domain 2
23:39:19.756 INFO mux > domain detached panes: []

Anything else?

No response

@cprusprus cprusprus added the bug Something isn't working label Mar 10, 2024
@handdara
Copy link

I thiink this is related to #2731?

@cprusprus
Copy link
Author

I suppose? That resolution just says only use one Unix domain. Or don't use domains at all since they're crippled and just use workspaces instead. Except that that means Wezterm is crippled and not a replacement for e.g. TMux. Which is unfortunate, since the idea was that it could be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants