This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: nesting "source" scripts
- To: csw@epigram.com
- Subject: Re: nesting "source" scripts
- From: DJ Delorie <dj@envy.delorie.com>
- Date: Sun, 21 Feb 1999 18:19:00 -0500
- CC: cygwin@sourceware.cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- In-reply-to: <8C36CEF2AF34D211922D00A0C9D60A5405A2B4@epimail.epigram.com>(message from Christopher Warth on Sun, 21 Feb 1999 14:59:15 -0800)
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- References: <8C36CEF2AF34D211922D00A0C9D60A5405A2B4@epimail.epigram.com>
- Sender: cygwin-owner@sourceware.cygnus.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@sourceware.cygnus.com