Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BBFE62F.9030802@ece.gatech.edu>
Date: Sun, 07 Oct 2001 01:20:47 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: Fergus on Linux <fergus AT bonhard DOT uklinux DOT net>
CC: cygwin AT cygwin DOT com
Subject: Re: Blindly running setup.exe to update Cygwin
References: <000501c14e9e$fea96c40$4c7b1f3e AT leper> <3BBF8FA0 DOT 2040207 AT ece DOT gatech DOT edu> <000d01c14ede$7d2ea640$4c7b1f3e AT leper>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

[back on list]

Fergus on Linux wrote:

>>That should not happen.  Do you still have the setup.log file from that
>>run of setup.exe, or have you already run setup again since then?  Also,
>>send you /etc/setup/installed.db file, please.
>>
> 
> Thank you very much for your kind interest.
> 
> I enclose as attachments to this email both the files setup.log and
> installed.db as they are after a single run of setup.exe as a new user
> installing Cygwin for the first time from the network.
> 
> By a "broken" vim I mean [at least] (a) strange lack of information about
> mode: "INSERT" not shown at bottom of screen even when in insert mode; (b)
> first use of <UpArrow> seems equivalent to <Esc>; (c) loss of syntax
> colours. I have checked that TERM=cygwin: it does.


Okay, this is not what I thought you were talking about.  I thought 
"broken" vim meant a popup window that said "Can't find 
cygncurses5.dll", and vim wasn't runnable at all.  *THAT'S* the thread 
you refered to.

Your vim "works" -- it just doesn't work like the the old 5.7 version 
did.  Well, that has nothing to do with libncurses -- I'm sorry I misled 
you. This is probably due to massive internal changes in vim, as it went 
from version 5 to version 6 (note that alpha and beta test phases of 
vim6 took over a year! so there's bound to be lots of changes).

I think you're going to have to take this up on the vim mailing list; it 
is doubtful that these changes are due to anything cygwin specific.


> 
> PS. I suppose the problem could lie with vim v.6 or term* rather than the
> installation procedure? 


I don't think it's the terminfo database.  Very little changed therein 
in the recent update.

> (There seem to be several problems with vim reported
> recently.) 


Most of the recent reports were much more serious: "vim won't start" or 
"missing DLL".  Your report is "merely" a fit-and-finish issue.

> Or with me! Such a bother: I've observed regular if infrequent
> complaints about setup.exe on the mailing list, and always dismissed them as
> symptoms of user-brain/-digit dysfunction rather than any inherent fault in
> setup.exe. Now I'm in the same situation myself. Thanks again for your
> response.


Again, I think that setup.exe is not the culprit in your case -- 
especially as your later private email showed no improvement in these 
fit-and-finish issues after reinstalling libncurses5.

Suggestion: assume that the problem is your .vimrc, and begin debugging 
from there.  I wonder if old .vimrc's are somehow incompatible (older 
vim's supported keywords that newer vim's do not?  Therefore if you use 
one of those "bad" keywords you have problems, but since I (by luck) 
avoid them -- whatever they are -- I don't see your problems?)

Anyway, this looks like a vim issue, not cygwin nor setup nor ncurses.

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/