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

[Yuri]

On 11/13/24 14:48, #!microsuxx wrote:
> 1st source cmd , no extra cmds 2. { . foo ; code ; code ; } | tee 3rd 
> tee < <( . foo ; cmds ) 


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.


Yuri