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

OS X giving "no current client" when using rename_session #117

Closed
tony opened this issue Apr 28, 2018 · 1 comment
Closed

OS X giving "no current client" when using rename_session #117

tony opened this issue Apr 28, 2018 · 1 comment

Comments

@tony
Copy link
Member

@tony tony commented Apr 28, 2018

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:

tony added a commit that referenced this issue Apr 28, 2018
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.
@tony tony closed this Apr 28, 2018
@eli-schwartz
Copy link

@eli-schwartz eli-schwartz commented Jul 4, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants