Date: Wed, 01 Nov 2023 03:49:33 +0000 From: Jamie Landeg-Jones <jamie@catflap.org> To: jamie@catflap.org, dickey@his.com Cc: freebsd-current@FreeBSD.org, bapt@FreeBSD.org Subject: Re: Freebsd 14+ -- tcsh incompatible with terminfo Message-ID: <202311010349.3A13nX1M094463@donotpassgo.dyslexicfish.net> In-Reply-To: <ZUGZPWBSt80p3jHa@prl-debianold-64.jexium-island.net> References: <202310312245.39VMjNJB080965@donotpassgo.dyslexicfish.net> <202310312259.39VMxm6W081150@donotpassgo.dyslexicfish.net> <ZUGZPWBSt80p3jHa@prl-debianold-64.jexium-island.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Dickey <dickey@his.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202311010349.3A13nX1M094463>