Apologies for dropping this on the floor. I just had a quick look at
this, but the rendering looks OK from here with the Konsole I have
available at the moment. Are you still seeing this problem? If so, do
you see it with XTerm as well?
(I don't see any non-ASCII characters, so our common issues with Unicode
don't seem to apply here. My best guesses are that either the termios
window size somewhere in the chain is out of sync with reality, or that
there's an issue with line wrap/automargins in one of the 3 terminal
emulators involved. But neither of these feel like good guesses.)
regards,
--jh
On 11/8/16 5:17 AM, Philipp Marek wrote:
>> We need you to run three separate invocations of "script", each one writing
>> to a different logfile.
>>
>> The first invocation will be before you even run mosh. Run something like
>> "script mosh_output" on your local machine.
>>
>> Then, *inside the resulting shell*, run "mosh server".
>>
>> Then, *inside that remote shell*, run "script tmux_output_and_mosh_input".
>>
>> Then, *inside the resulting shell*, run tmux.
>>
>> Then, *inside that*, run "script tmux_input".
>>
>> Then, *inside the resulting shell*, do whatever you can do to demonstrate
>> the problem.
>>
>> Then exit all the shells cleanly.
>>
>> The result will be two logfiles on the remote machine ("tmux_input" and
>> "tmux_output_and_mosh_input") and one logfile on the local machine
>> ("mosh_output").
>>
>> We'll need to examine all three logfiles to figure out where the problem is
>> happening.
> Okay, understood. You want _nested_ files.
>
> But "tmux" is local, so the counts are the other way around ;)
>
>
> Happens with 1.2.5 from jessie-backports, too; logfiles are attached.
> Just before the end I pressed Ctrl-L to restore the screen output; I hope
> that doesn't interfere with your investigations.
>
> $ tput cols ; tput lines
> 80
> 24
>
