We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The tmux tests will raise "no current client" because we are raising exceptions if stderr is returned.
https://github.com/tmux-python/libtmux/blob/v0.8.0/libtmux/session.py#L128
Related links:
The text was updated successfully, but these errors were encountered:
Fix issue #117 with rename-session on tmux 2.7
7443b60
tmux 2.7 on BSD systems (including macOS) can raise no current client. See Also: - https://www.mail-archive.com/tech@openbsd.org/msg45186.html - https://marc.info/?l=openbsd-cvs&m=152183263526828&w=2 This makes sure that rename_session won't raise the warning on OS X systems.
Not BSD-specific BTW, this error manifests on Arch Linux as well with an updated tmux.
https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/python-libtmux&id=3d24e5183a80421e8cb5a0a37d878d8399b2ff86
Sorry, something went wrong.
No branches or pull requests
The tmux tests will raise "no current client" because we are raising exceptions if stderr is returned.
https://github.com/tmux-python/libtmux/blob/v0.8.0/libtmux/session.py#L128
Related links:
The text was updated successfully, but these errors were encountered: