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: <4.3.1.2.20011119122920.0219bdb0@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 19 Nov 2001 12:37:24 -0500
To: "Daniel Meier" <dmeier AT crosstrust DOT com>, <cygwin AT cygwin DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: Setup.exe Revisited
In-Reply-To: <025301c1711e$d6a798f0$2701010a@crosstrust.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 12:23 PM 11/19/2001, Daniel Meier wrote:
>I've seen a couple of complaints but no real response to the question: setup.exe used to be (like, last week) real easy to run and install most things needed, but now it doesn't.
>  
>I mean after installing with setup.exe I can't even run vi! None of the cygwin directories are in the path. Even if I add them to the path it still can't find vi. 


Well, where is 'vi' on your system?  On my system, it's in /usr/bin/vi...


>I note that in the new install vim is not default. I assume there is a difference between vi and 'new improved vi' - vim. The most important difference being vi IS part of the default environment?


I'm not sure what you mean when you say 'vim' is "not default".  I'm also
not sure why you assume 'vi' and 'vim' are different.  You really shouldn't
do allot of assuming.  It doesn't help resolve any problems generally.

vi and vim are the same thing.


>  
>It used to take a brainless cluck to install and use cygwin. Now you've raised the entry requirement - must have a functional brain as well as a few clues. 


Perhaps you'll need to debug what's causing the problem on your end.  
This is certainly not typical behavior and the first thing to rule out
is a local configuration issue.  If you can provide details that indicate
that the problem is within setup itself, that would be a big help (a 
patch would be even better! ;-) )

Good luck,



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/