DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=pXbiUUoDXkitS7BPhK/98fhH9UxkV8RCHll7qL7cz3Cgb/YBkSdKv
	Ao3yTkg5lj2rP/q5LwND2KO3fJmbxfcApOZJBjF/h5f5ojtqyTzXXrgGw+eF8Xsp
	+ueE6L30lL/qHOoje+t2zi+dVt5ZEk4EmJEra/Q42EEf3kX614UX5g=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Andrew Schulman <schulman.andrew@epa.gov>
Subject: Re: fish PATH problem
Date: Thu, 09 Oct 2014 10:01:27 -0400
Lines: 42
Message-ID: <h43d3ap1d2s3d2hdms89160k19kr20vaiv@4ax.com>
References: <8du93aldjf5p3r29dcibokhu4dgps0lv21@4ax.com> <gk2a3aduk0idoqs1g1qjv3ij12gin3867p@4ax.com> <54350D2B.3050103@gmail.com> <BLU436-SMTP1501DF73E10EF914FF5A637E4A30@phx.gbl> <54365F3B.9010303@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> On 08/10/2014 18:36, Alive4Ever wrote:
> > On Wednesday, October 08, 2014 11:08:43 AM you wrote:
> >> Does that work. It seemed to have the same issue as noted in the
> >> following thread https://cygwin.com/ml/cygwin/2014-04/msg00111.html
> >>
> > It should work, although I don't recommend running cygwin apps directly
> > via wincmd, unless the underlying shell is invoked as interactive login
> > shell.
> So I just re-tested starting a fish login shell after updating cygwin64. 
> As I suspected, fish has not been updated since the thread I quoted (Apr 
> 2014), and the issue remains (with my install). Google doesn't show the 
> maintainer on list since the announcement (Oct 2013), and his e-mail 
> bounces. Cc'ing anyway, just in case.

If fish needs a new maintainer, it looks like not a hard package to
maintain.  It has a simple and up-to-date cygport script, and builds OOTB
with just one small source code patch.

> Andrew: appreciated if you can confirm whether simply invoking as a 
> login shell works for you.

It sort of works.  When I change my shell to /usr/bin/fish in /etc/passwd
and run 

C:\cygwin64\bin\mintty.exe -

I don't get any error messages, as I first reported.  But the environment
isn't set up correctly.  The main problem seems to be that although I'm
running 64-bit cygwin, the directory for 32-bit cygwin is mounted as the
root filesystem:

 ~> cygpath -w /
C:\cygwin

By comparison when I start fish from bash, I get:

aschulma@LC77E1AASCHULMA ~> cygpath -w /
C:\cygwin64

This is a pretty serious problem.  Any thoughts on why it happens?

Andrew


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple