X-Recipient: archive-cygwin@delorie.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:from:to:cc:mime-version
	:content-transfer-encoding:content-type:in-reply-to:references
	:subject:date; q=dns; s=default; b=KMgLEnOq9SsGHrFWwJCqYdqBjTzcu
	skrB7yzcG/W0VmE4Xl2GE1JmRHLwP4VZsapsNC1xHzv1lON1fhxsNvcAG9/e0UWO
	/n1I+8Uva7t7rQF/ob8pLc07QW3Yq+bGd2A5W9WjF4/f9FkfsfxyzAXLrLjVWmAa
	u+mMIPEyMBKshI=
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:from:to:cc:mime-version
	:content-transfer-encoding:content-type:in-reply-to:references
	:subject:date; s=default; bh=jCLRsToepb1bT+IgXIuSQHyo7d0=; b=UQQ
	6OYURAEsoAxY8ejqSQZnKaAEsCp9UmRyxNFCwuYVqTBpQbTHeeN41p0FKdtOe+zU
	LL8xPTXPOUJG0MnT2LTnnbh4HPELN0PFakqH4yFUZAIL1w9Uxzmhk4HHtUPnYfgK
	4ahVkeP6PAiJUQ8wWv1e31EeT2OF0aG05/et25k4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: out1-smtp.messagingengine.com
Message-Id: <1397124355.23022.284E4ADE@webmail.messagingengine.com>
From: Ronald Fischer <ynnor@mm.st>
To: Dave Kilroy <kilroyd@googlemail.com>, cygwin@cygwin.com
Cc: glitchmr@myopera.com
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
In-Reply-To: <534452B8.2030909@gmail.com>
References: <534452B8.2030909@gmail.com>
Subject: Re: Possible bug with chere 1.4 when configuring for fish
Date: Thu, 10 Apr 2014 12:06:15 +0200

> I've had more time to look around. If you add the following to the file 
> ~/.config/fish/config.fish (create it if you haven't already got one), 
> then things should work as intended:
> 
> if status --is-login
> 	set PATH /usr/local/bin /usr/bin $PATH
> end
> 
> Alternatively drop it in the fish global startup file, 
> /usr/share/fish/config.fish. 

I tried the variant of putting it into the global startup file, it
doesn't resolve the problem for me. I'll play around a bit with it as
soon as I have time (I'm a first-time user of fish and am busy with
other things right now, so this might take some time).

Ronald
-- 
Ronald Fischer <ronaldf@eml.cc>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)


--
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

