Mon premier blog

Termcap and Terminfo by John Strang, Linda Mui, Tim O'Reilly

Termcap and Terminfo John Strang, Linda Mui, Tim O'Reilly ebook
Publisher: O'Reilly Media
Format: djvu
ISBN: 0937175226, 9780937175224
Page: 139

Pour savoir � quoi elle ressemble pour votre terminal en cours : $ infocmp -I. Setenv TERMINFO /usr/share/lib/terminfo setenv TERMINFO /usr/local/share/terminfo. Because vt100 compatible terminals have that concept of a "normal" and "application" mode, you either have to set the terminal to the mode you want to use, or find the termcap/terminfo sequences for both modes. This information is stored in the system terminfo or termcap database. Yeah, it's got to be a termcap/terminfo issue. I had some headache with the readline dependency to termcap/ncurses/terminfo. >> >> I found this page useful : >> https://bugzilla.redhat.com/show_bug.cgi?id=499837 >> >> I think that we will at least need ncurses. Whether your system is using termcap or terminfo is an historical thing – Linux/SysV based systems tend to use terminfo, BSDish systems termcap. On the Unix server side, depending on you configuration of software called termcap on you os. Termcap étant devenue une base de données un peu grosse, sa structure et sa syntaxe ont été modifiées et c'est devenu terminfo. If I do an "export TERM=linux" and then rerun by .bash_profile, it highlights compressed files in red, directories in blue, executables (or those with the execute bit set) in green. And then there are the terminals (xterm, gnome-terminal, KDE console, etc.). There are termcap and terminfo databases, there is X which has a say in the whole matter, and there are the individual applications themselves.