byobu-quiet fails on tmux due to non-existing option -X

[Christoph Lange]

My actual problem with

$ byobu --version
byobu version 5.18
tmux 1.6

from the Gentoo ebuilds running in Konsole 2.8.4 (KDE 4.8.4) is the one that has been reported at http://askubuntu.com/questions/143370/byobu-doesnt-show-the-colourful-status-line – I don't see a status line. For enabling it I tried the following, which failed, as byobu is trying to invoke tmux with the non-existing option -X:

$ byobu-quiet --undo
tmux: unknown option -- X
usage: tmux [-28lquvV] [-c shell-command] [-f file] [-L socket-name]
            [-S socket-path] [command [flags]]

This has also been reported before at http://askubuntu.com/questions/143370/byobu-doesnt-show-the-colourful-status-line, but with this post I'd just like to confirm it, and to point out that any code like $BYOBU_BACKEND -X won't work in tmux, at least not in version 1.6.

Here are the other occurrences of such code:
$ fgrep -- "BYOBU_BACKEND -X" `qlist byobu`
/usr/lib64/byobu/date: [ "$bd" = "0320" ] && msg="$(printf "%s" SGFwcHkgQmlydGhkYXkgU2NyZWVuIC0tIGh0dHA6Ly9iaXQubHkvc2NyZWVuLWJkYXkK | base64 -di)" && $BYOBU_BACKEND -X -S "byobu" at "*" echo "[$msg]"
/usr/bin/byobu-ctrl-a: $BYOBU_BACKEND -X at 0 source "$BYOBU_CONFIG_DIR/profile"
/usr/bin/byobu-ctrl-a: $BYOBU_BACKEND -X at 0 source "$BYOBU_CONFIG_DIR/profile"
/usr/bin/byobu-disable: $BYOBU_BACKEND -X at 0 quit
/usr/bin/byobu-quiet:$BYOBU_BACKEND -X at 0 source "$BYOBU_CONFIG_DIR/profile"
/usr/bin/byobu-select-profile: $BYOBU_BACKEND -X at 0 source "$BYOBU_CONFIG_DIR/profile"

[Christoph Lange (allegristas)]

Oh, I _do_ actually see a status line, but not as intended.

There _is_ apparently a status line that shows the open windows starting from the left (much like tmux's default). I can even switch if off and on using tmux's :set status off/on. But it doesn't show all the status notifications I've set up using the Byobu configuration menu. (Well, in fact I didn't do much; I'd just like to have the default status notifications for now, but I'm not getting them.)

Maybe this should be a separate ticket, but I'm not sure I can describe this bug sufficiently well.