Hmm, okay, I did reproduce this once, but I'm not able to reproduce it
now. Here's what I've tried...
1) backend == tmux, running byobu inside of byobu:
kirkland@x220:~$ byobu
sessions should be nested with care. unset $TMUX to force.
2) backend == tmux, running byobu-tmux inside of byobu:
kirkland@x220:~$ byobu-tmux
sessions should be nested with care. unset $TMUX to force.
3) backend == tmux, running byobu-screen inside of byobu
(launches a new byobu-screen session)
4) backend == screen, running byobu inside of byobu:
kirkland@x220:~$ byobu
Attaching from inside of screen?
5) backend == screen, running byobu-tmux inside of byobu:
(launches a new byobu-tmux session)
6) backend == screen, running byobu-screen inside of byobu:
kirkland@x220:~$ byobu-screen
Attaching from inside of screen?
** Changed in: byobu (Ubuntu)
Status: Confirmed => In Progress
** Changed in: byobu (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/911500
Title:
byobu (screen) goes nuts when running nested byobu (tmux)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/911500/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs