From owner-freebsd-current@freebsd.org Wed Mar 31 13:56:52 2021 Return-Path: Delivered-To: freebsd-current@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 2E87B5790B0 for ; Wed, 31 Mar 2021 13:56:52 +0000 (UTC) (envelope-from SRS0=cMgG=I5=FreeBSD.org=otis@ns2.wilbury.net) Received: from ns2.wilbury.net (ns2.wilbury.net [92.60.51.55]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "svc.wilbury.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F9SY00BJJz3Ndb for ; Wed, 31 Mar 2021 13:56:51 +0000 (UTC) (envelope-from SRS0=cMgG=I5=FreeBSD.org=otis@ns2.wilbury.net) Received: from [10.3.0.135] (hq.bonet.sk [92.60.48.52]) (Authenticated sender: juraj@lutter.sk) by svc.wilbury.net (Postfix) with ESMTPSA id 0793445CF04; Wed, 31 Mar 2021 15:56:43 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Subject: Re: 13.0-RC3 bison causes tputs SIGSEGV From: Juraj Lutter In-Reply-To: Date: Wed, 31 Mar 2021 15:56:42 +0200 Cc: Thomas Dickey , FreeBSD-current@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <20210329233138.GA4334@prl-debianold-64.jexium-island.net> <33EE2402-4447-4168-AB5B-D98009CD03AA@FreeBSD.org> <20210331004803.GA1607@prl-debianold-64.jexium-island.net> To: Henric Jungheim X-Mailer: Apple Mail (2.3608.120.23.2.4) X-Rspamd-Queue-Id: 4F9SY00BJJz3Ndb X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2021 13:56:52 -0000 > On 31 Mar 2021, at 15:53, Henric Jungheim wrote: > >> >> So... the question I have is what is $TERM in this case, >> and where is the related terminal description (in terminfo or termcap). > > In the example in my original email, $TERM was "xterm-256color" > (connected through "Windows Terminal" running MS' ssh on Win10). In my case, also xterm-256color, connected using iTerm2 on macOS. otis