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

[#!microsuxx]

another code is

if u wanna not use . or eval or bash cmd
( . is source )

shopt -s expand_aliases
alias script=" $( < user.bash ) "
script

On Thu, Nov 14, 2024, 1:10 AM #!microsuxx <fxmbsw7@gmail.com> wrote:

> also u need to $log
> may i ask what criteria ur scripts are about
>
> a $log can be
>
> log=/tmp/my.log.$USER.$SRANDOM
>
> On Thu, Nov 14, 2024, 1:04 AM #!microsuxx <fxmbsw7@gmail.com> wrote:
>
>> maybe ur email formats it wrong
>> those are two lines , by greg
>> not one
>>
>> anyway if u append more than one cmd to logfile
>> more than one source cmd
>> u need to use >>logfile instead of >logfile
>>
>> On Thu, Nov 14, 2024, 1:00 AM #!microsuxx <fxmbsw7@gmail.com> wrote:
>>
>>>
>>>
>>> On Thu, Nov 14, 2024, 12:57 AM Yuri <yuri@rawbw.com> wrote:
>>>
>>>> On 11/13/24 15:44, Greg Wooledge wrote:
>>>> > If the "user script" runs quickly enough, then: source userscript
>>>> > >logfile 2>&1 cat logfile
>>>>
>>>>
>>>> This would fail to save the user script's output in case it would
>>>> execute "exit 1"
>>>>
>>>
>>> the >logfile makes it overwrite
>>> just from the two quoted lines
>>>
>>>>
>>>>
>>>> Yuri
>>>>
>>>>
>>>>
>>>>