Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Mon, 24 Apr 2000 11:18:11 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: symblinks problem Message-ID: <20000424111811.A8702@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: ; from matt@use.net on Mon, Apr 24, 2000 at 02:23:30AM -0700 On Mon, Apr 24, 2000 at 02:23:30AM -0700, Matt wrote: >On the 4/23/2000 snapshot, there seems to be inconsistency in following >symblinks. > >In /home/src/i586-pc-cygwin/winsup, there is a symblink from configure.in >to ../.././winsup/configure.in . When I 'vi configure.in' while the >working directory is /home/sec/i586-pc-cygwin/winsup , it doesn't follow >the symblink to the original file, it instead shows me the contents of the >symblink: !../.././winsup/configure.in > >An strace log is attached ('bash -c "vi configure.in"', where the cwd is >the one mentioned above). As far as I can tell from the strace, you aren't running a cygwin version of 'vi'. cgf