Hi list,
seems I found a regression: When attaching, tmux does not reliably
choose the most recently used /unattached/ session anymore.
The following commands show the issue: (run them within 60s)
$ tmux new -d 'echo nobody attaches to me ...; sleep 60'
$ tmux new -d 'timeout 60 watch tmux ls'
$ xterm -e tmux a & sleep 1
$ xterm -e tmux a & sleep 1
[...]
All xterms attach to the second session, even when it already
has several clients attached and the first session has none.
Then I compiled and run older (stable) tmux binaries and found:
2.0 and 2.1 attach like this:
xterm1: session2
xterm2: session1
xterm3: session1
[...]
2.2 and 2.3 (and git) attach like this:
xterm1: session2
xterm2: session2
xterm3: session2
[...]
All test were done without any tmux.conf's around.
I observed this behavior for quite a while now before I spent
the time investigate. (Until today I thought it was an error
in a script I wrote to run tmux remotely via ssh.)
I /think/ it did not happen before I upgraded to 2.3. I may
be wrong here, or it might be a combination of tmux and its
libraries:
$ ldd /usr/bin/tmux
libutil.so.1 => /lib/libutil.so.1 (0xf772e000)
libncurses.so.6 => /lib/libncurses.so.6 (0xf76d6000)
libevent-2.0.so.5 => /usr/lib/libevent-2.0.so.5 (0xf768c000)
libresolv.so.2 => /lib/libresolv.so.2 (0xf7675000)
libc.so.6 => /lib/libc.so.6 (0xf74c5000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf74a9000)
/lib/ld-linux.so.2 (0xf7750000)
Can anyone confirm the issue?
Thomas
--
You received this message because you are subscribed to the Google Groups
"tmux-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.