You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(For context--My team is new to tmux. Overmind has been a fantastic process management solution in conjunction with turborepo for us).
Use case:
Connect to one overmind/tmux session per Mac OS Terminal tab
We'd like to be able to open multiple tabs in Terminal, and run overmind connect [service] once per tab, with a different service per tab. However, currently, when connecting to more than one service in this way, tmux treats it as the same session and essentially makes ALL tabs view the same window (tmux has a concept of one current/active window per session).
Is there a way to disable this behavior, or create a new session per overmind connect [service] call, and move the tmux window for that service into that session?
The text was updated successfully, but these errors were encountered:
Whenever a new client attaches, this creates a new session within the same overmind session-group (a session-group shares all windows within all sessions), and switches to the same window_index as was current before creating the new session.
This is allows us to open a different "current window" in each new Terminal tab.
(For context--My team is new to tmux. Overmind has been a fantastic process management solution in conjunction with turborepo for us).
Use case:
We'd like to be able to open multiple tabs in Terminal, and run
overmind connect [service]
once per tab, with a different service per tab. However, currently, when connecting to more than one service in this way, tmux treats it as the same session and essentially makes ALL tabs view the same window (tmux has a concept of one current/active window per session).Is there a way to disable this behavior, or create a new session per
overmind connect [service]
call, and move the tmux window for that service into that session?The text was updated successfully, but these errors were encountered: