From nobody Wed Nov 01 19:37:26 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SLHMs14m0z4yw2G for ; Wed, 1 Nov 2023 19:37:29 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SLHMr6wLQz3Y4S; Wed, 1 Nov 2023 19:37:28 +0000 (UTC) (envelope-from bapt@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698867449; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=m20E5s4OT6AFpO8rFCOTROgwRgmZU28CN6UcYTyS5Ww=; b=JzI4wBVy1HmOeBHP+9rmij/QMzBC0jvFWL9EdTDCA9gBoAdbVwiDBtp67slK4u58okCjbE 13oWouCB57OI8XwNuH4TQlfdxOq1L6ah5amR+KWamlbbOscRTB2qjiuiSUubroMQ+nUfT2 UgP2P9ZZSSmspL1HofzHHl+Ev+AQ48I6kU/F2DWBd4TGQLPQU4IW2QixABo1iyUSzVxepW BUgC0yWE5bfZqToOQ8nSecFUzQpsAoQvXiYk6ilFLa7yf4ewYUHHZZGf59Ku3/3ycExEMF anqDQTJbs4Xa0y6bIfFEWLLmbeMxOFp9o5YtNiJCl0M8Dwtxn1rNfbIQf6ZvmQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1698867449; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=m20E5s4OT6AFpO8rFCOTROgwRgmZU28CN6UcYTyS5Ww=; b=C2kytCARMB9u+QucaxZGD6IbjhMqaOe8LNi1ZUBUADveyIQIHcKhAcu2Y71uy62TQUPa8T 5Mz2cVduWdTKA9QY8Pisf0jgWimmbdYKRdhZeivz/RwqZsUdqcpfUhprngP/lR41WNDvSU CAGXS4gbZawOqEXSuk2ZN3ChYFkCL9iBilY/awrL01SebWAfzqssopiTKpJWqlpTUpYrb1 pSJ4sihvxnecXO6rP3TqIwti2sH+6ZtYI2Vfzc/tJFtEkwRWC1exRD1U4/1yCaIixSkn+z Knqh/Mc1vowU/T1x2PgrMcCUaPEGkzAvsUdBaUUGbTnrM2oQyvAY0522ofjRXg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1698867449; a=rsa-sha256; cv=none; b=ySXVSFJD1gtpFHdGq2rMVNdv8k5MmJWz0hZzISXxlO/V9JBkOgRaOR7EUdbhPUctqadIB0 xGzJP3zy+oA61YBoj+KmZ6SC09P1/qmLlMi4zlrbby6lj5iwpGhl/jQ5Kh3D4VVa0GT8+S vAdUu+PbbwrqOrISPBtG7M0oM6wjXQfhCInREWZFvEqV6EAj6eRuHYqW16ZOW+xG4rRFU0 GLDIyfpQazWxKVRwrrDDgB9CQHQm/ScNCwjn50DHSpUxnnBCLAKGgsa7ZR+b78O+9HGd0b RLgCOor4WQEbqyLWElEZzDAbJzB9tjZoS+f+nK0+ssLPtslXJ7RhLZ3a7+bFbw== Received: from aniel.nours.eu (nours.eu [176.31.115.77]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 4SLHMr5Kn2z1GMR; Wed, 1 Nov 2023 19:37:28 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id D91C711E485; Wed, 1 Nov 2023 20:37:26 +0100 (CET) Date: Wed, 1 Nov 2023 20:37:26 +0100 From: Baptiste Daroussin To: Jamie Landeg-Jones Cc: dickey@his.com, freebsd-current@freebsd.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo Message-ID: References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> On Wed, Nov 01, 2023 at 03:49:33AM +0000, Jamie Landeg-Jones wrote: > Thomas Dickey wrote: > > > actually it probably does affect "xterm" > > > > Checking the source, tcsh is expecting a termcap string, while data read > > from the terminfo database is going to be in terminfo format -- even if > > read via tgetent/tgetstr > > > > tcsh is expecting a termcap string, and in its EchoTC function it duplicates > > the termcap version of what's tparm in a terminfo program. > > > > (tcsh could be modified readily to use terminfo for the case you're describing, > > but supporting $TERMCAP would be work) > > Hi Thomas, thanks for the reply... from the ncurses man himself! > > I *thought* I'd seen issues with just "xterm" but after posting the first > message, it seemed to start working, and so I doubted myself, but I must > have messed up somewhere! > > What threw me about tcsh is it does mention terminfo in the man page and > the source, so I wrongly assumed the problem wasn't there. > > Anyway, I'll raise it with the tcsh maintainers. > > To the FreeBSD release folk, I think it's great that we're moving off termcap, > but is there a chance that base tcsh could be compiled with a private version > of the terminfo-less ncurses in time for 14.0-RELEASE, if a proper fix to tcsh > is going to take too long? > > Thanks again, Thomas. > > Cheers, Jamie If you don't install (terminfo-db which nothing should pull in by default), then you are on the default behaviour which is termcap, this has been made like this on purpose, by default you have the behaviour you have always expected, and if you want another behaviour and larger support you install terminfo-db. The fact that tcsh does not play nicely with terminfo, is nother problem. Best regards, Bapt