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=AAGUYu8xvDBr+Y4pwE89Q4ErT4cwdW6DGK3WkTnUxcUKFG/GYWArI
	K/WLsZG7k69jypdrlvtxORn8o/w41NkSWACt7nx/vB9NaepYxC9vlWTWIZCMm6km
	VAPmt52kv59FKndJCuZ6X9Zxe+zvxlzITPafQZ+dNph56sxRsHBGc8=
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: Fri, 10 Oct 2014 09:46:11 -0400
Lines: 49
Message-ID: <vijf3adncvnnu3b0dh9h8qbjk4i58p0b8d@4ax.com>
References: <8du93aldjf5p3r29dcibokhu4dgps0lv21@4ax.com>     <gk2a3aduk0idoqs1g1qjv3ij12gin3867p@4ax.com> <54350D2B.3050103@gmail.com>   <BLU436-SMTP1501DF73E10EF914FF5A637E4A30@phx.gbl> <54365F3B.9010303@gmail.com>   <h43d3ap1d2s3d2hdms89160k19kr20vaiv@4ax.com>  <988061198.20141009192356@yandex.ru>  <o0ed3ad7127d18huch47u43eohod98hsu9@4ax.com> <1938036834.20141009212648@yandex.ru> <54370457.8060905@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> On 09/10/2014 18:26, Andrey Repin wrote:
> > Greetings, Andrew Schulman!
> >
> >> Bad news: the PATH problem is back.  When I run
> >> C:\cygwin64\bin\fish.exe -l
> >> I get the same error messages as before on startup, and PATH doesn't
> >> include /bin /usr/bin /sbin /usr/sbin.
> >> How are /bin /usr/bin etc. normally added to the PATH?  I don't see any
> >> logic to do it in /usr/share/fish/config.fish.
> > That logic probably should be included.
> > At least, bash does that in login files.
> >
> 
> That was my conclusion as well*. Question is, should fish provide the 
> configuration, or should base-files cover all shells?
> 
> Andrew: thanks for confirming. If you're still looking for the logic and 
> where to put it, I suggested something in * as well.

OK, I rolled a new release of fish 2.1.1:

x86:
http://home.comcast.net/~andrex2/cygwin/x86/fish-2.1.1-1.tar.xz
http://home.comcast.net/~andrex2/cygwin/x86/fish-2.1.1-1-src.tar.xz

x86_64:
http://home.comcast.net/~andrex2/cygwin/x86_64/fish-2.1.1-1.tar.xz
http://home.comcast.net/~andrex2/cygwin/x86_64/fish-2.1.1-1-src.tar.xz

It adds the following improvements in /etc/fish/config.fish:

* Prepends /usr/local/bin /bin to PATH.  This solves the PATH errors for me.

* Changes to the home directory in login shells.

* sources all scripts /etc/profile.d/*.fish.  So far I think there are few or none of
those, but once fish supports them, some will start to appear, especially if we can
get cygport to start creating them.

I think that's the best answer to your question about base-files.  I looked in
/etc/profile to see if it might be made to support fish too, but I don't think so.
It's too sh-centric.  fish's syntax is too different.  So if fish supports
/etc/profile.d on its own, then we can just leave it at that.

Please try it out, and let me know how it works for you.  If it's okay and if Konrad
doesn't answer, then I'll adopt the package and put out the new release.  I've
switched to using fish as my default shell now, so I want to see it maintained.

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