tmuxifier inside existing tmux session causes errors

[joshgillies]

A workflow I'm trying to achieve would allow me to spin up tmux sessions at will. However it seems as though if I'm currently inside a tmux session I get the following errors:

➜  ~ tmuxifier s example-session
can't find window example-window
couldn't set 'allow-rename'
➜  ~

Any idea?

[GeeF]

At least for me this also happens outside of tmux, if the name of the session differs from the filename.
Correction: It happens, if the window title is the same for multiple windows in a session.

[wilmoore]

I've also noticed this; however, I've simply worked around it by detaching first, then loading the new session.

[joshgillies]

@wilmoore totally, I've come to the same conclusion. Not ideal but it works.

I think the reason it hit this in the first place, was I wanted to be able to spawn other sessions based from a "parent" session.

Eg. tmuxifier s app which itself calls tmuxifier s db-server && tmuxifier s api-server

[wilmoore]

Yup, same thing here. 👍

[breneser]

Same problem here, and I am starting a new tmux instance whenever I open a terminal window. That's why it is kind of annoying not being able to load a session inside a tmux session.

Is there a plan to fix this?

[cappuMUC]

I've stumbled over this issue while trying tmuxifier. The cause of the issue is that the session isn't specified in the set-option command for allow-rename so tmux defaults to the current session. I've opened a pull request for the fix.

[rodhash]

The "detaching" workaround apparently works only if we manually detach, right?

Would be nice if we'd be able to add this detach in the session script .. in my tests it doesn't quite work tho:

if initialize_session "css"; then
 tmux detach-client
...