-
Notifications
You must be signed in to change notification settings - Fork 49
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
Ignore switching message after connect command #149
Comments
I think we should add some command options, such as --silent to prevent this behavior @joshmedeski |
That's a good idea. The plan is to add logging (#140) so this message isn't really necessary. |
I'll come up with something and get it pushed. |
Done, wait a few minutes and you should be able to update sesh to 2.0.2 which does not output any messages when running the connect command. |
p.s. you can remove the |
Thank @joshmedeski for your swift response. |
What would you like sesh to do?
I've just upgraded from v1 to v2 after some of the issues from v1 have been fixed. Unfortunately, my normal workflow of the tmux+fzf+sesh has been broken, as after calling connect in tmux+fzf, the switching happens with a successfully switching message that makes the tmux session not show up immediately.
The text was updated successfully, but these errors were encountered: