Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 8 Nov 2002 15:33:25 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: vi won't execute - symlink semantics changed? Message-ID: <20021108153325.I21920@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20021108051641 DOT 687E3340A1 AT nevin DOT research DOT canon DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021108051641.687E3340A1@nevin.research.canon.com.au> User-Agent: Mutt/1.3.22.1i On Fri, Nov 08, 2002 at 04:16:41PM +1100, luke DOT kendall AT cisra DOT canon DOT com DOT au wrote: > I updated my Cygwin installation to the latest version, yesterday. > (That included the fresh bash-2.05-7 and binutils.) > > Since then, I can't run vi except by either specifying the full path > /usr/bin/vi or using vim. In other words, the symlink from vi -> > vim.exe does not get used. > > I also notice that if you do a test -x /usr/bin/vi that now fails; I > believe it used to succeed. I checked both with 1.3.15-2 and can't reproduce it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/