Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Sun, 21 Feb 1999 18:19:00 -0500
Message-Id: <199902212319.SAA00554@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: csw AT epigram DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <8C36CEF2AF34D211922D00A0C9D60A5405A2B4@epimail.epigram.com>
	(message from Christopher Warth on Sun, 21 Feb 1999 14:59:15 -0800)
Subject: Re: nesting "source" scripts
References:  <8C36CEF2AF34D211922D00A0C9D60A5405A2B4 AT epimail DOT epigram DOT com>


Sorry, my linux bash does exactly the same thing you describe.  If you
must call scripts based on $0, you can't use "source" to do it.
Perhapst the "eval" builtin might help work around this?

> This looks like it is simply a bash bug rather than anything specific
> to cygwin but snce I encountered this using cygwin I will try to find
> the answer here first.
> 
> It looks like the full path name of bash scripts is not available when
> they are invoked with "source".  This makes it impossible to call
> other scripts in the same directory, no?

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com