-
Notifications
You must be signed in to change notification settings - Fork 110
Server.has_session() erroneously reports session exists with tmux 2.5 #67
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
Comments
After doing a "tmux kill-server", I can't reproduce the issue. It's looks like previously the tmux server had stayed running after the last session finished. I'm not immediately finding a way to get it back into that state. |
Untested fix in pull-request #68 |
I can't think of how to recreate it, but that'd be helpful in making a testcase for it. |
This issue has been automatically marked as stale because it has not had This bot is used to handle issues where the issue hasn't been discussed or |
tmux from MacPorts (on macOS 10.12.6), recently updated to tmux 2.5.
Tmuxp erroneously reports the session already exists when trying to load the session.
Some light debugging points to libtmux/server.py:Server.has_sessions() does not account for 'tmux has-session' now responds with 'no current session'.
The text was updated successfully, but these errors were encountered: