X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Olhe03XJm3RK8BE8zLBmT3u++7UO0qZKM3ocVSKeiy1
	pTshFYdZDuUI00THMQ17ltlrXSgDDa2CwKgc0HNcFeHIg+TYrwu1fOEr0nqFeIxK
	BpJenUD+jYEriuNn+/9bL2xo0BqM4K++MO2IPTZ/IynNVnkedYas+3vcV51b0Grg
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=Jcsbt8e1pgsem5mqvVwS2My52Ns=; b=c8MXLWIzvTKeUCMMM
	6c9zuDB+ajoeA2lqoF8hQwTWL8W6e6r5zjpr3i6VI0aGrfcvaA6rvngGgL+XhCVQ
	gqFGqHUWZ5r8GDY+jMZPeipQ8LsreRND4Xhiz0Mx0WYg5N6G3+bDpwxwIpI00PE/
	uQfp9EufFhlPhikZ9/PEucVB3I=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2
X-HELO: BLU004-OMC1S17.hotmail.com
X-TMN: [/9qd72PHKG1mUaTMjI5c+1fGcfXzjYou]
Message-ID: <BLU436-SMTP24110F1AB0E1E5F479807B6E4A10@phx.gbl>
Date: Fri, 10 Oct 2014 22:19:37 +0700
From: Alive <alive4ever AT live DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: fish PATH problem
References: <8du93aldjf5p3r29dcibokhu4dgps0lv21 AT 4ax DOT com> <BLU436-SMTP370BD9033BAFA915C06FEFE4A30 AT phx DOT gbl> <gk2a3aduk0idoqs1g1qjv3ij12gin3867p AT 4ax DOT com> <54350D2B DOT 3050103 AT gmail DOT com>
In-Reply-To: <54350D2B.3050103@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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