This is the mail archive of the
mailing list for the Cygwin project.
Re: fish PATH problem
- From: Andrew Schulman <schulman dot andrew at epa dot gov>
- To: cygwin at cygwin dot com
- Date: Fri, 10 Oct 2014 11:27:07 -0400
- Subject: Re: fish PATH problem
- Authentication-results: sourceware.org; auth=none
- References: <8du93aldjf5p3r29dcibokhu4dgps0lv21 at 4ax dot com> <BLU436-SMTP370BD9033BAFA915C06FEFE4A30 at phx dot gbl> <gk2a3aduk0idoqs1g1qjv3ij12gin3867p at 4ax dot com> <54350D2B dot 3050103 at gmail dot com> <BLU436-SMTP24110F1AB0E1E5F479807B6E4A10 at phx dot gbl>
> On 08/10/2014 17:08, Dave Kilroy wrote:
> > On 08/10/2014 10:57, Andrew Schulman wrote:
> >>> On Wednesday, October 08, 2014 05:13:54 AM Andrew Schulman wrote:
> >>>> When I try to start fish directly from the Windows shell instead of
> >>>> from
> >>>> bash, I get a boatload of errors, like this:
> >>> I suggest you to read fish manual page, and find how to invoke fish
> >>> as login
> >>> shell. On bash and zsh, there is '-l' flag so that they behave with
> >>> fresh
> >>> environment variables.
> >> Doh! Right. Thanks.
> > 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
> > Dave.
> I've tested launcing `fish -l -i` from wincmd. A lot of errors shown.
> I think `fish` is not yet optimized to be `default shell` for cygwin.
> There are still more works to be done to make it usable as cygwin login
Please try the updated fish 2.1.1 package I just posted, and see if it fixes those
problems for you. Exit all running fish shells, then run:
tar -Jx -C/ -f fish-2.1.1-1.tar.xz
Then try starting fish as a login shell.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple