On 2007-06-03, Kamaraju Kusumanchi <[EMAIL PROTECTED]> wrote:
> Hi
> 
>     I installed vim 7.1 via cygwin on Windows XP machine. However, 
> when I run vim on the bash shell of cygwin, I am getting the
> following error.
> 
> E558: Terminal entry not found in terminfo
> 'cygwin' not known. Available builtin terminals are:
>     builtin_riscos
>     builtin_amiga
>     builtin_beos-ansi
>     builtin_ansi
>     builtin_pcansi
>     builtin_win32
>     builtin_vt320
>     builtin_vt52
>     builtin_xterm
>     builtin_iris-ansi
>     builtin_debug
>     builtin_dumb
> defaulting to 'ansi'
> 
> Can anyone help me get rid of this error. This error stays on the 
> screen for about 3 seconds. Then it disappears and the vim screen 
> appears.
> 
> Any ideas?

Something seems to be wrong with your Cygwin installation.  I have 
installed the vim 7.0 packages from Cygwin, built vim 7.0 from 
Cygwin sources, and recently built vim 7.1 from vim.sf.net sources 
on Cygwin and I have never seen that error.

I think 'infocmp' is part of the default cygwin installation, so you 
should have it.  Execute it in the same bash shell you used to run 
vim and see what you get.  The first three lines should look like 
this.

#       Reconstructed via infocmp from file: /usr/share/terminfo/c/cygwin
cygwin|ansi emulation for Cygwin,
        am, hs, mir, msgr, xon,
        colors#8, it#8, pairs#64,

That will verify that your terminfo database is properly installed 
and readable.  If you get something else, it may indicate what the 
problem is.

Something else you might do is execute

   vim --version

and report here what you get.  Seeing the whole thing might be
useful, but I am particularly interested in the last line, which
should look something like this,

   Linking: gcc   -L/use/local/lib -o vim.exe   -lncurses  -liconv

and will show whether or nor your vim was linked with the ncurses
library.

HTH,
Gary

-- 
Gary Johnson                 | Agilent Technologies
[EMAIL PROTECTED]     | Mobile Broadband Division
                             | Spokane, Washington, USA

Reply via email to