It seems tmux alone, in a single instance (no tmux within tmux) breaks 256 colors as well. NB: I have not configured tmux in any way, just running it like "tmux" from a fresh SSH shell. I also found that the problem of broken 256 color support in nested sessions persists when switching backends to "screen".
So it seems the following is true:
1) Single Byobu instance with tmux backend works with 256 colors
2) Single tmux instance breaks 256 colors (probably a configuration issue)
3) Byobu instance (tmux) within Byobu (tmux) breaks 256 colors
4) Tmux instance within tmux: breaks 256 colors (as before)
5) Single Byobu instance with screen backend works with 256 colors
6) Byobu instance (screen) within Byobu (screen) breaks 256 colors
So I think Byobu is somehow responsible, because it seems to be the common element here.
Sorry, totally forgot to follow up.
It seems tmux alone, in a single instance (no tmux within tmux) breaks 256 colors as well. NB: I have not configured tmux in any way, just running it like "tmux" from a fresh SSH shell. I also found that the problem of broken 256 color support in nested sessions persists when switching backends to "screen".
So it seems the following is true:
1) Single Byobu instance with tmux backend works with 256 colors
2) Single tmux instance breaks 256 colors (probably a configuration issue)
3) Byobu instance (tmux) within Byobu (tmux) breaks 256 colors
4) Tmux instance within tmux: breaks 256 colors (as before)
5) Single Byobu instance with screen backend works with 256 colors
6) Byobu instance (screen) within Byobu (screen) breaks 256 colors
So I think Byobu is somehow responsible, because it seems to be the common element here.
Can I do anything else to debug this?