Update of bug #48848 (project screen):
Status: Works For Me => Confirmed
_______________________________________________________
Follow-up Comment #8:
So I posted why we end up with "screen.xterm" or alike in previous comment.
I think it's more of discussion if we want screen to behave the way it is or
force user input.
I would also assume that user input as long as it's correct takes precedence
over how it behaves currently, so it should probably first check user passed
value and if there is not corresponding termcap proceed with other checks.
And yes, reproduced it:
% echo $TERM
xterm-256color
% screen -c /dev/null -T screen
% echo $TERM
screen.xterm-256color
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?48848>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
