Date: Fri, 26 Feb 2021 21:19:35 +0100 From: Jan Beich <jbeich@FreeBSD.org> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: Baptiste Daroussin <bapt@FreeBSD.org>, src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: Re: git: 2a50a9de8340 - main - terminfo: add terminfo database Message-ID: <blc6-fup4-wny@FreeBSD.org> References: <202102251327.11PDR4eC083842@gitrepo.freebsd.org> <202102261420.11QEKJoX006569@slippy.cwsent.com> <20210226143714.k24aacsrjnnhkktc@aniel.nours.eu> <202102261448.11QEmHlA006761@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Cy Schubert writes: > Baptiste Daroussin writes: >> I was planning to MFC it to 13.1, I don't know how much this change >> is a POLA violation or not, imho all the other benefice of terminfo >> over termcap for end users are worth the MFC, but if most people >> vote against, I won't MFC it. > > I think this is big enough not to MFC to 13.1. To keep POLA on 13.1 ncurses needs to look into termcap and if it can't find a match there look into terminfo. Old entries like xterm would keep working like before (ti/te disabled) while new entries like xterm-direct2, alacritty, etc. will behave like upstream intended (smcup/rmcup enabled). However, I haven't looked into ncurses source how easy it'd be to implement. >From ports/ perspective having terminfo as fallback would be enough. termcap -> terminfo conversion is often lossy and requires writing outside of /usr/local (aka PREFIX). For example, many modern terminals source xterm-256color but it's not maintained (e.g., bug 247447)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?blc6-fup4-wny>