tmux, launch_msg(): Socket is not connected

[ColinHebert]

When I start automatically tmux I get this message.

After a small hunt, it seems that it comes from tmux new-session -d -s "$tmux_session" "$SHELL -l" in the tmux plugin, in particular the "$SHELL -l" part (it's not just the -l option, it's the entire argument).

I'm not sure that's important to force the shell like this, I removed it and it still works.

[sorin-ionescu]

It's telling tmux to launch a login shell. I remember that error. It believe it's a tmux bug. You'll have to google.

By the way, tmux is pretty buggy. I had the thing crash OS X multiple times with kernel panics. I had to power cycle the machine.

[ColinHebert]

Yes, I've already done my research. It doesn't seem to be due to tmux (well, not entirely), but to launch_ctl .
I know it's to start a login shell, but I wonder if it's important to force it.

The documentation states that by default, default-command is executed, and if default-command isn't set

The default is an empty string, which instructs tmux to create a login shell
using the value of the default-shell option.

And by default, default-shell

When started tmux tries to set a default value from the first suitable of the SHELL environment variable,
the shell returned by getpwuid(3), or /bin/sh.

So that's basically what tmux is already doing.

[sorin-ionescu]

Ok. Then I suppose it's safe to remove. The screen plugin was written first and the tmux plugin is based on it.

[ColinHebert]

Just, more information on the issue: https://github.com/ChrisJohnsen/tmux-MacOSX-pasteboard

If you don't use this reattach-to-user-namespace you will still have the issue.
Right now I have

set-option -g default-command "reattach-to-user-namespace -l $SHELL -l"

in my .tmux.conf and it works fine.

[sorin-ionescu]

Right, I use that to make pbcopy/pbpaste work. How does it behave on Linux?