From owner-freebsd-questions@freebsd.org Wed Apr 29 15:22:02 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2C72F2B8351 for ; Wed, 29 Apr 2020 15:22:02 +0000 (UTC) (envelope-from ypankov@fastmail.com) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49C2LK0gc2z4MMG for ; Wed, 29 Apr 2020 15:22:00 +0000 (UTC) (envelope-from ypankov@fastmail.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id ADCCC5C02DF; Wed, 29 Apr 2020 11:22:00 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 29 Apr 2020 11:22:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=W hH3DewRPJUndS2k2rcT7BESedOYQ3Dm2ycIOmMBGhs=; b=IVUlbGPzeeCwToxfk tA8Jo+T+opDG9PDIe+Ob6c3RLBzacPw5aFDl2ywT1RzMVSakBXiHYaLZKUIY+CQ9 6QarN9g8CUj5feDCwhHmG5UcFDrhIQslj5E7VVwEsap3hnI4XmRz28LUPZD7aWt3 PiprfQF9Tw0WCRv6HCJyVxQYgoc2bVP7T0fOWAbnHz81Y5vOysKO0k22xgLUtELG vciI8SNH3Rx4fDyDg2HxCmfnXO8mlCZIE85oH0eQJS3nINZUcKJ1x3H8OpNJwhn0 3baQTAGXjZESV+pjj6h8RQ9pmvwKZNNjvI0eNTioGVwvcTjsTMrX7/OiBBWFB7oy 81eBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=WhH3DewRPJUndS2k2rcT7BESedOYQ3Dm2ycIOmMBG hs=; b=HPnwcpKfoQxp3giUEAn4XdNirXHzmgAGx6MhQn2FtlPX3aZ8rUp1mN2mn /T5QXenDGwRKNMxdfqWB/qeQkYg8oTqMphfKObfNmmxs0Yftm/dDFvuDZOOYsCXa DvYgLl/0ApW849EOV8tpuhhSvzGUuz4Ni9fL4ABDSAoep7rtIhA8ZMByaYdj8q8r SsNFYFH4z2DmGS+acXyOJT3YA0XUHI3/UzDSU9HmFrXxOiRiFcK8h2rw63xguNVL 5JdNlwT+i4BoZkDawNONUW6lVnwawKscUZ0s6BAqEzpsTQ7p2c5HLw3sfcOhPxjV DPbqsKRCB5kzNm3uFOJi5R/QWYEYw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrieefgdekjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthejre dttdefheenucfhrhhomhepjghurhhiucfrrghnkhhovhcuoeihphgrnhhkohhvsehfrghs thhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepgffggfevfeektddvvdetueeutd ejjefgveehueekveehhfevfeevtdefvdduhfeinecuffhomhgrihhnpehfrhgvvggsshgu rdhorhhgnecukfhppeekhedrudejgedrvddtjedrvddujeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihphgrnhhkohhvsehfrghsthhmrghi lhdrtghomh X-ME-Proxy: Received: from [192.168.1.6] (unknown [85.174.207.217]) by mail.messagingengine.com (Postfix) with ESMTPA id E49143065EF9; Wed, 29 Apr 2020 11:21:58 -0400 (EDT) Subject: Re: sysutils/screen and its now default "screen.xterm-256color" terminal type To: Victor Sudakov , freebsd-questions@freebsd.org References: <20200429150458.GA1475@admin.sibptus.ru> From: Yuri Pankov Message-ID: <9dc5f37c-11f3-4b08-9b0c-fd45442e51ac@fastmail.com> Date: Wed, 29 Apr 2020 18:21:58 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <20200429150458.GA1475@admin.sibptus.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49C2LK0gc2z4MMG X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=fastmail.com header.s=fm2 header.b=IVUlbGPz; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=HPnwcpKf; dmarc=pass (policy=none) header.from=fastmail.com; spf=pass (mx1.freebsd.org: domain of ypankov@fastmail.com designates 66.111.4.27 as permitted sender) smtp.mailfrom=ypankov@fastmail.com X-Spamd-Result: default: False [4.96 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(0.00)[+ip4:66.111.4.27:c]; FREEMAIL_FROM(0.00)[fastmail.com]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[fastmail.com:+,messagingengine.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(0.00)[fastmail.com,none]; RECEIVED_SPAMHAUS_PBL(0.00)[217.207.174.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[fastmail.com]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[27.4.111.66.list.dnswl.org : 127.0.5.1]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_XBL(5.00)[217.207.174.85.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.4]; R_DKIM_ALLOW(0.00)[fastmail.com:s=fm2,messagingengine.com:s=fm2]; NEURAL_HAM_MEDIUM(-0.80)[-0.799,0]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; IP_SCORE_FREEMAIL(0.00)[]; BAD_REP_POLICIES(0.10)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.86)[0.856,0]; IP_SCORE(0.00)[ip: (-9.83), ipnet: 66.111.4.0/24(-4.89), asn: 11403(-2.69), country: US(-0.05)] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2020 15:22:02 -0000 Victor Sudakov wrote: > Dear Colleagues, > > Have you noticed that the recent versions of sysutils/screen force the > setting of $TERM to "screen.xterm-256color"? FreeBSD does not know this > terminal type, which leads to different errors in programs running under > screen ("using dumb terminal" etc). > > I've opened a PR > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246029 but the > maintainer is too quick to close it IMHO. > > Does anyone care to view/comment on the PR? $ screen --version Screen version 4.08.00 (GNU) 05-Feb-20 Not a screen user myself, I just installed the latest screen from ports to check, and not seeing this behavior: without ~/.screenrc I get $TERM of "screen", and with "term xterm256-color" in ~/.screenrc I get exactly that in $TERM. What are your other related settings? Or could it be stale system-wide configuration somewhere, stale patches?