Re: HEADS UP: terminfo imported into -current

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        Hello.  And the advantages of terminfo over termcap are, exactly,
what, again?  Why are we making this change?  Was it discussed on the
lists?  What does it buy us?  Solaris did this, and it was a pain in the
proverbial backside 15 years ago.  And, I'm not sure it made things better,
even to this day.  I'm not against having termcap and terminfo, but I think
we should discuss the merrits of this change  before doing it.

-thanks
-Brian
On Feb 3,  6:24pm, Christos Zoulas wrote:
} Subject: Re: HEADS UP: terminfo imported into -current
} On Feb 3,  3:47pm, tls%panix.com@localhost (Thor Lancelot Simon) wrote:
} -- Subject: Re: HEADS UP: terminfo imported into -current
} 
} | On Wed, Feb 03, 2010 at 05:24:54PM +0000, Roy Marples wrote:
} | >
} | > A quick look at the code suggests this is to purely set the number of  
} | > columns and lines in the window. A lot of applications respect $COLUMNS  
} | > and $LINES - would it not be better (and more portable) to set those?
} | 
} | Why exactly is it that $TERMCAP support was removed?  This seems like
} | a wholly different change from simply implementing terminfo -- and a
} | bad one.
} 
} It would require someone to parse the option and convert it to a terminfo
} description and use it. There is code to convert captoinfo, but I don't
} think it is part of the library.
} 
} christos
>-- End of excerpt from Christos Zoulas