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:from:to:mime-version
	:content-transfer-encoding:content-type:in-reply-to:references
	:subject:date; q=dns; s=default; b=jmPNUnt0bW/Zq3iWRXn5NpOBOR7wM
	eZ9dnEkF66E7j6QlBX2l8u2uIpWLgeOS9Cvwt3lKhcWM1uAmyonGchHxuxL9G8UX
	TdyemfEKtj6tMMB0h+Ok5GX7K0L+wupdc2IgD/tjpk48M3BndtBu0zCZQ5pAakpz
	ewzbHw/SobO8Yw=
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:mime-version
	:content-transfer-encoding:content-type:in-reply-to:references
	:subject:date; s=default; bh=Cd6SVf6UTY57BLJ7fnZhVx2adKQ=; b=UFX
	08ro8BtzNFXRwMfPAUku6OVkGlLutEuCaJVZWiv5SUQpPTuqiOciIaUIwIi6di9X
	7NgVFL0FWK4rdjaobSS/6r23wTmgrRXdH4f5M2ZCJ1n+sMJERjA5lgryJIJA3w8t
	Wjdaa4LolSoK7T+ae7HXt0lmxOcxdQo0T27vwlSI=
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=-0.4 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: out1-smtp.messagingengine.com
Message-Id: <1397031536.11971.104446677.670024A0@webmail.messagingengine.com>
From: Ronald Fischer <ynnor AT mm DOT st>
To: Dave Kilroy <kilroyd AT googlemail DOT com>, cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
In-Reply-To: <5343282E.7080004@gmail.com>
References: <5343282E DOT 7080004 AT gmail DOT com>
Subject: Re: Possible bug with chere 1.4 when configuring for fish
Date: Wed, 09 Apr 2014 10:18:56 +0200

On Tue, Apr 8, 2014, at 0:35, Dave Kilroy wrote:
> On 07/04/2014 13:02, Ronald Fischer wrote:
> > I have installed fish 2.1.0. Works fine, when invoking a new fish shell
> > manually.
> >
> > However, when doing a
> >
> >     chere -ifcm -t mintty -s fish
> >
> > and invoke the new fish shell from the Windows Explorer context menu, I
> > get plenty of error messages, like this:
> >
> > <snip>
> >
> Thanks for the report.
> 
> I've just checked my x86_64 and x86 installation. Things are working on 
> my installation as I have c:\cygwin\bin on my standard windows path. 
> When I remove it and invoke fish, I get the errors that you highlight. 
> Similarly when echo'ing $PATH under the broken fish, /usr/bin is not one 
> of the entries.

Indeed: Once I'm adding the cygwin bin path to my windows system
environment, it works, so this is at least a temporary workaround (on
the long run, I don't want to have the cygwin path permanently set on
this machine).

> I need to have a play around to see how I can fix this, but I thought 
> cygwin prepended /usr/bin to the path...

I don't think "cygwin" by itself changes the path. It certainly doesn't
change the Windows system path (as defined in the "Advanced System
Settings" for Windows).

However, when I start a bash shell, /usr/bin is part of the PATH. This
happens inside /etc/profile. But this file is not always processed; This
depends on how bash is started. You can see the detailed rules in the
bash man-page, in the section INVOCATION.

My guess is that when doing a chere -2 fish, you start via bash in a way
that /etc/profile is not read. 

As for chere -1 fish, I suspect that this will never work, unless the
user has put the Cygwin bin path into his system PATH. Maybe in this
case, chere should output a warning message.

Ronald
-- 
Ronald Fischer <ronaldf AT eml DOT 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