Re: The 'source x' command doesn't keep variables set by x when source output is piped into other command

[#!microsuxx]

i agree
its hard to , say , comm clearly together

i suggest for next times more real life true examples
op's msgs werent so much detailed , more bla-neric :))

greets all

On Thu, Nov 14, 2024, 1:35 AM Robert Elz <kre@munnari.oz.au> wrote:

>     Date:        Wed, 13 Nov 2024 15:18:58 -0800
>     From:        Yuri <yuri@rawbw.com>
>     Message-ID:  <c14967fc-4df9-4332-97f2-c7195dde33b5@rawbw.com>
>
>   | I need to (1) source the user script, (2) save this script's output to
> a
>   | dedicated file, (3) keep the same output in stdout, and (4) keep
>   | environment variables that the user script sets for later commands.
>   | It doesn't look like any of the above 3 lines do all these 4
> requirements.
>
> Sometimes you can't always have what you need - there probably are
> methods here, but before solving this problem someone should find out
> whether it really needs to be solved.
>
> That is, far too often people determine what they think they need to do
> to solve some problem,  discover that what they think they need to do is
> hard, so ask for help doing that hard thing - often with mixed results.
>
> If there was an explanation of what the issue really is that led you to
> believe that you need those 4 things, perhaps someone might be able to
> show you that you really don't - that this is not the correct approach
> to solving the real problem, and there is a much better way.
>
> But as long as you continue chasing down this rabbit hole, that will
> never happen.
>
> kre
>
>
>