This is the mail archive of the cygwin 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] |
Is it deliberate and desirable to have less(1) not be terminfo-aware? Splitting the terminal capability database into several files certainly makes it easy to install the entry for a new terminal type. Background: I've been porting a terminal emulator (http://www.jessies.org/~enh/software/terminator/) to Cygwin. It has its own terminfo entry which it installs. After doing this, less(1) still produces the dreaded: WARNING: terminal is not fully functional I think I've tracked this down to less.exe not being linked to the terminfo-aware ncurses library: $ cygcheck /usr/bin/less.exe C:/cygwin/bin/less.exe C:\WINNT\system32\KERNEL32.dll C:\WINNT\system32\NTDLL.DLL C:/cygwin/bin\cygwin1.dll C:\WINNT\system32\ADVAPI32.DLL C:\WINNT\system32\RPCRT4.DLL C:/cygwin/bin\cygpcre-0.dll $ If I build with libncurses-devel installed, less's configure script notices, I get a dependency on C:\cygwin\bin\cygncurses-8.dll and the resulting less.exe works fine with "terminator". ------------------------------------- Martin's Outlook, BlueArc Engineering
Attachment:
cygcheck.out
Description: cygcheck.out
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |