This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: fish PATH problem
- From: Alive <alive4ever at live dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 10 Oct 2014 22:19:37 +0700
- 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>
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
shell.
For a quick comparison, `bash -l -i` and `zsh -l -i` works fine, even
when launched via wincmd. The PATH environment is set up correctly with
them, so that there is no problem to use bash and zsh for cygwin login
shell.
--
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