-
-
Notifications
You must be signed in to change notification settings - Fork 833
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
Closing last wezterm window should not terminate the mux server (by design?) #631
Comments
This has been a commonly requested feature in the past week, and it's a reasonable one. The mux server inherited the close-when-done behavior from when it used to be an alternate front-end in the same executable as the gui, but it doesn't need to be that way any more. We also need to accomodate that case in the client: if the newly attached domain doesn't result in any panes being imported, we need to spawn a new command there in order to keep the client alive. The pre-existing check for whether the mux was empty had false positives because the local mux may still reference the pane from the connection UI, which would finish closing out shortly after we had decided not to spawn anything, and then the client would close. refs: #631 refs: #507
Yeah, that's a fair request. This behavior was by design, but that design was from when the mux server was a separate front-end within the same binary as the GUI. |
Thanks for the quick fix @wez ! There's one remaining minor issue: After some digging it seems like the actual error is |
propagate the likely client destroyed error instead refs: #631
I couldn't directly reproduce this, but I did just push a commit that might help. Let me know how it works out! |
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
Closing the last window somehow would terminate the mux server today.
Environment (please complete the following information):
To Reproduce
Enable multiplexing:
server:
client:
After connection is established, ctrl d to terminate the session and close the window.
Reconnect and connections is refused. Check server side the mux server is not running any more.
Configuration
don't think this is actually relevant here
Expected behavior
The server process should not quit and reconnection should be successful.
Additional context
The text was updated successfully, but these errors were encountered: