On Thu, May 7, 2020 at 10:35 AM Rodney W. Grimes <
freebsd-...@gndrsh.dnsmgr.net> wrote:
> > Hello everyone,
> >
> > I can't find any proper rationale in our history (maybe I missed it)
> which
> > explains why our ncurses is stuck on using termcap(5) instead of
> terminfo(5)
> > Except an
> Hello everyone,
>
> I can't find any proper rationale in our history (maybe I missed it) which
> explains why our ncurses is stuck on using termcap(5) instead of terminfo(5)
> Except an argument in the Makefile that builds ncurses:
> "Used instead of the hideous read_termcap.c abomination."
>
On Thu, May 07, 2020 at 03:22:20PM +0200, Mateusz Piotrowski wrote:
> Hi,
>
> On 5/7/20 2:41 PM, Baptiste Daroussin wrote:
> > Hello everyone,
> >
> > I can't find any proper rationale in our history (maybe I missed it) which
> > explains why our ncurses is stuck on using termcap(5) instead of
Hi,
On 5/7/20 2:41 PM, Baptiste Daroussin wrote:
Hello everyone,
I can't find any proper rationale in our history (maybe I missed it) which
explains why our ncurses is stuck on using termcap(5) instead of terminfo(5)
Except an argument in the Makefile that builds ncurses:
"Used instead of the
Just my one cent.
Baptiste Daroussin wrote in
<20200507124126.g4z5op4cyv45p...@ivaldir.net>:
|I can't find any proper rationale in our history (maybe I missed it) which
|explains why our ncurses is stuck on using termcap(5) instead of terminf\
|o(5)
...
|I would like to make the move from
Hello everyone,
I can't find any proper rationale in our history (maybe I missed it) which
explains why our ncurses is stuck on using termcap(5) instead of terminfo(5)
Except an argument in the Makefile that builds ncurses:
"Used instead of the hideous read_termcap.c abomination."
Which I do not
