-
Notifications
You must be signed in to change notification settings - Fork 109
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
It doesn't work well with wemux #25
Comments
I haven't really used wemux. Mind elaborating a bit on said hacks? Off the top of my head I'd imagine the main issue is specifying which server socket to talk to right? If that's the issue, I enable passing custom options to tmux, via extra arguments, or a |
I would also like to pass additional arguments to tmux, especially the socket name. I am using the following wrapper in ~/bin, which tmuxifier picks app from $PATH:
tmuxinator has a socket_name setting for specifying the socket. |
The |
Actually I'm re-opening this issue as 0.9.0 doesn't exactly fix the main topic of this issue. Add a socket_name argument to tmuxifier is on my todo list. And I'll also give wemux a properly try together with tmuxifier to see what else I can do to make it easier. |
Has there been any movement on this issue? |
Or at least I can't manage to get it working without a lot of ugly hacks :(
The text was updated successfully, but these errors were encountered: