This is the mail archive of the cygwin-developers mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On some systems, libtermcap is now actually a gateway to the terminfo database, maybe even using libncurses.We should consider termcap dead at this point. I don't even have a /etc/termcap on my most recent Ubuntu and gentoo systems and I obviously haven't missed it.
...tcsh uses termcap as well, unfortunately. The reason is the existence of libtermcap.a. tcsh checks for the termcap functions in this order:
libc -> libtermcap -> libcurses -> libncurses.
I tried to argue with the upstream maintainers to prefer the moreAnd it's legitimate for them to make the assumption I tried to suggest above.
modern library, but they argue for the least footprint solution.
However, if we drop the libtermcap.a file from the distro, the nextDropping libtermcap *and* /etc/termcap is a proper solution (although not nice for the manual lookup use case...).
tcsh will automatically use ncurses.
So, I'm all for getting rid of the termcap package and only keepIn this case, my other comment (from other mail) applies: keep it up-to-date or delete it. Wasn't there a tool in the xterm (or ncurses) package to generated /etc/termcap automatically from the terminfo database?
some sort of /etc/termcap file...
I should read mails completely before I start to reply to them...So, I wouldn't mind if it was either removed or subsumed by ncurses...preferredly generated from the info files.
since every linux distro that I know of which still has it seems to
generate it from infotocap.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |