Nested sessions allowed? #146

Closed
rkoch opened this Issue Oct 19, 2015 · 10 comments

Comments

Projects
None yet
2 participants
@rkoch

rkoch commented Oct 19, 2015

I just installed v2.1 on Mac OS X 10.10, iTerm 2 via homebrew.

On v2.0 it was not possible to create nested sessions:

$ tmux
sessions should be nested with care, unset $TMUX to force

Now on v2.1, this seems to have changed and nested sessions are possible by default, although it wasn't mentioned in the release notes. Is this expected or a bug?

Thanks for clarifying.

@nicm

This comment has been minimized.

Show comment
Hide comment
@nicm

nicm Oct 19, 2015

Contributor

Works for me, does it work if you do:

tmux -f/dev/null -Ltest sh -c 'tmux -Ltest new; sleep 1000'

On Mon, Oct 19, 2015 at 01:26:24AM -0700, Remo Koch wrote:

I just installed v2.1 on Mac OS X 10.10, iTerm 2 vi homebrew.

On v2.0 it was not possible to create nested sessions:

$ tmux
sessions should be nested with care, unset $TMUX to force

Now on v2.1, this seems to have changed and nested sessions are possible
by default, although it wasn't mentioned in the release notes. Is this
expected or a bug?

Thanks for clarifying.

--
Reply to this email directly or [1]view it on GitHub.

Reverse link: [2]unknown

References

Visible links

  1. #146
  2. #146
Contributor

nicm commented Oct 19, 2015

Works for me, does it work if you do:

tmux -f/dev/null -Ltest sh -c 'tmux -Ltest new; sleep 1000'

On Mon, Oct 19, 2015 at 01:26:24AM -0700, Remo Koch wrote:

I just installed v2.1 on Mac OS X 10.10, iTerm 2 vi homebrew.

On v2.0 it was not possible to create nested sessions:

$ tmux
sessions should be nested with care, unset $TMUX to force

Now on v2.1, this seems to have changed and nested sessions are possible
by default, although it wasn't mentioned in the release notes. Is this
expected or a bug?

Thanks for clarifying.

--
Reply to this email directly or [1]view it on GitHub.

Reverse link: [2]unknown

References

Visible links

  1. #146
  2. #146

@nicm nicm closed this Oct 20, 2015

@rkoch

This comment has been minimized.

Show comment
Hide comment
@rkoch

rkoch Oct 20, 2015

Sorry, didn't have the time to test it until now.

It works fine when I run the command above without the sh. Could this be something with my configs?

rkoch commented Oct 20, 2015

Sorry, didn't have the time to test it until now.

It works fine when I run the command above without the sh. Could this be something with my configs?

@nicm

This comment has been minimized.

Show comment
Hide comment
@nicm

nicm Oct 20, 2015

Contributor

But does exactly what I said work?

Contributor

nicm commented Oct 20, 2015

But does exactly what I said work?

@rkoch

This comment has been minimized.

Show comment
Hide comment
@rkoch

rkoch Oct 20, 2015

In that case not:

$ tmux -f/dev/null -Ltest sh -c 'tmux -Ltest new; sleep 1000'
ambiguous command: sh, could be: show-buffer, show-environment, show-messages, show-options, show-window-options

rkoch commented Oct 20, 2015

In that case not:

$ tmux -f/dev/null -Ltest sh -c 'tmux -Ltest new; sleep 1000'
ambiguous command: sh, could be: show-buffer, show-environment, show-messages, show-options, show-window-options
@nicm

This comment has been minimized.

Show comment
Hide comment
@nicm

nicm Oct 20, 2015

Contributor

OOps, sorry it should be:

tmux -f/dev/null -Ltest new sh -c 'tmux -Ltest new; sleep 1000'

Contributor

nicm commented Oct 20, 2015

OOps, sorry it should be:

tmux -f/dev/null -Ltest new sh -c 'tmux -Ltest new; sleep 1000'

@rkoch

This comment has been minimized.

Show comment
Hide comment
@rkoch

rkoch Oct 20, 2015

Okay this works!

A new tmux session is started and the usual sessions should be nested with care, unset $TMUX to force message is printed on the screen.

rkoch commented Oct 20, 2015

Okay this works!

A new tmux session is started and the usual sessions should be nested with care, unset $TMUX to force message is printed on the screen.

@nicm

This comment has been minimized.

Show comment
Hide comment
@nicm

nicm Oct 20, 2015

Contributor

What if you just do this:

tmux -f/dev/null -Ltest new

Then try "tmux -Ltest new" yourself inside that tmux. Does it work?

Contributor

nicm commented Oct 20, 2015

What if you just do this:

tmux -f/dev/null -Ltest new

Then try "tmux -Ltest new" yourself inside that tmux. Does it work?

@rkoch

This comment has been minimized.

Show comment
Hide comment
@rkoch

rkoch Oct 20, 2015

This works as well:

Inside the new tmux session:

$ tmux -Ltest new
sessions should be nested with care, unset $TMUX to force

rkoch commented Oct 20, 2015

This works as well:

Inside the new tmux session:

$ tmux -Ltest new
sessions should be nested with care, unset $TMUX to force
@nicm

This comment has been minimized.

Show comment
Hide comment
@nicm

nicm Oct 20, 2015

Contributor

Ok so it is probably your config somehow. Does it still not work with
your full config? What is in your .tmux.conf?

On Tue, Oct 20, 2015 at 02:11:08AM -0700, Remo Koch wrote:

This works as well:

Inside the new tmux session:

$ tmux -Ltest new
sessions should be nested with care, unset $TMUX to force

--
Reply to this email directly or [1]view it on GitHub.

Reverse link: [2]unknown

References

Visible links

  1. #146 (comment)
  2. #146 (comment)
Contributor

nicm commented Oct 20, 2015

Ok so it is probably your config somehow. Does it still not work with
your full config? What is in your .tmux.conf?

On Tue, Oct 20, 2015 at 02:11:08AM -0700, Remo Koch wrote:

This works as well:

Inside the new tmux session:

$ tmux -Ltest new
sessions should be nested with care, unset $TMUX to force

--
Reply to this email directly or [1]view it on GitHub.

Reverse link: [2]unknown

References

Visible links

  1. #146 (comment)
  2. #146 (comment)
@rkoch

This comment has been minimized.

Show comment
Hide comment
@rkoch

rkoch Oct 20, 2015

Hm that's soo weird - now it works! My system was probably in a weird state before..

Anyway thanks for your help & sorry for the false alarm :)

rkoch commented Oct 20, 2015

Hm that's soo weird - now it works! My system was probably in a weird state before..

Anyway thanks for your help & sorry for the false alarm :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment