Package: tmux
Version: 2.3-4
Followup-For: Bug #892503
(Note that I'm reporting the bug as found in the older tmux that is the
outer tmux of a tmux-in-tmux situation, though the proposed work-around
is to be applied to the newer tmux that is the inner tmux. This is
to (hopefully) properly mark the
Hi,
On Sat, Mar 31, 2018 at 6:39 AM, Vagrant Cascadian wrote:
> Though, while using backports works around the issue, it would be ideal
> to get it fixed in stretch as well...
Yes, unfortunately that requires identifying the real root cause and
which of hundreds of changes between 2.3 and 2.6 fi
On 2018-03-11, Romain Francoise wrote:
> On Fri, Mar 9, 2018 at 8:45 PM, Vagrant Cascadian wrote:
>> I've got a tmux (2.3-4) session running on a stretch machine, from which
>> I ssh to a buster machine and run tmux (2.6-3). In both cases,
>> TERM=screen. When the output reaches the bottom of the
Hi,
On Fri, Mar 9, 2018 at 8:45 PM, Vagrant Cascadian wrote:
> I've got a tmux (2.3-4) session running on a stretch machine, from which
> I ssh to a buster machine and run tmux (2.6-3). In both cases,
> TERM=screen. When the output reaches the bottom of the screen, the
> output gets garbled, leav
Package: tmux
Version: 2.6-3
Severity: normal
Many thanks for maintaining tmux! I use it constantly!
I've noticed a new problem with tmux on at least two buster machines,
but I have not observed it on any stretch machines.
I've got a tmux (2.3-4) session running on a stretch machine, from which
5 matches
Mail list logo
