This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: symblinks problem
- To: cygwin-developers at sourceware dot cygnus dot com
- Subject: Re: symblinks problem
- From: Matt <matt at use dot net>
- Date: Mon, 24 Apr 2000 12:41:34 -0700
On Mon, 24 Apr 2000, Chris Faylor wrote:
> 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: !<symlink>../.././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'.
This is really weird, the cygwin installer didn't appear to install it's
own vi anywhere; that's not supposed to happen, is it? I'll wipe this
installation and try the newsetup.exe, assuming that vi is supposed to be
installed :)
Sorry for the false alarm, I didn't think I had another vi on this system.
I'll try to be more observant next time.
--
this band is perfect
just don't scratch the surface