Path: csiph.com!goblin3!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Ilkka Virta <itvirta@iki.fi>
Newsgroups: gnu.bash.bug
Subject: Re: Have var+func sourced in a subroutine but they don't seem to end up in same scope
Date: Mon, 29 Jul 2019 19:25:54 +0300
Lines: 25
Approved: bug-bash@gnu.org
Message-ID: <mailman.155.1564417568.1985.bug-bash@gnu.org>
References: <5D3E9154.2030007@tlinx.org> <9f1ca322-09f6-a151-e13f-a053cf0ab89a@iki.fi>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
To: L A Walsh <bash@tlinx.org>, bug-bash <bug-bash@gnu.org>
Envelope-to: bug-bash@gnu.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
In-Reply-To: <5D3E9154.2030007@tlinx.org>
Content-Language: en-US
Precedence: list
Xref: csiph.com gnu.bash.bug:15259

On 29.7. 09:25, L A Walsh wrote:
> The library-include function allows me to source a library file
> that is in a relative path off of PATH (a feature not in bash,
> unfortunately).

[...]

> I tried putting exporting the data and the function with export
> but it ended up the same.  The variables weren't defined in the
> same scope as the function.

Are you sourcing some other script, or running it as a regular program?

Because above, you say 'source', which would indicate running code from 
another file in the same shell, but then you talk about exporting, which 
really only matters when starting a new process (as far as I know).


An example that would actually run and demonstrate the issue might make 
it easier to see what's actually going on.


-- 
Ilkka Virta / itvirta@iki.fi