Am 13.07.2017 um 11:20 schrieb Martin Steigerwald:
> Sven Joachim - 13.07.17, 10:16:
>> On 2017-06-22 16:03 +0200, Axel Beckert wrote:
> […]
>> > What caused it and how to mitigate it:
>> >
>> > Not yet tested, but suspected to mitigate this is to uninstall
>> > ncurses-term from the Stretch machine on which screen is running and
>> > then exiting and starting the screen session again.
>>
>> A less drastic measure is to change the TERM variable before running
>> screen, e.g. to xterm.
>
> Ideally I think screen would recognize that the remote machine doesn´t have
> the terminal description and try from fallback terminal (i.e.
> "screen-256color" which appears to work nice on all Debian 8, CentOS 7, SLES
> 12). Like:
>
> fallbackterm screen-256color screen
>
> But that would be an upstream feature request and I am not sure whether it is
> reasonably possible to implement it. If so, I am willing to create one.
It is not possible at all because screen cannot even notice that you're
intending to connect to a remote machine, much less read that machine's
terminal database. Only programs on the remote machine can notice that
there's no terminal entry for your $TERM, and since they have no clue
what terminal emulator you use, they cannot provide a fallback either
(except "dumb" perhaps, which is not too useful).
Cheers,
Sven
