Run scripts from within bashrc instead of sourcing them about synth-shell

[andresgongora]

It's quite problematic. Some scripts, like fancy_bash_prompt, MUST be sourced. So, there are two options:

1. All scripts are sourced, but those that don't need it do everything possible to avoid polluting the environment, like wrapping themselves in a single huge function, which then gets called in a subshell, and is finally unset

status()
{
##All extra functions here
foo()
{

}

## Main code here
do-status-stuff
foo
}

## Call here
(status)
unset status

2. Modify the installer such that some files get sourced, and others instaled

[olmari]

I'd vote for the solution 1 in general, but this is only opinion...

Wouldn't it be sufficient to add just that 'unset status' to current end of status.sh?

(Where does current system leaves variables? I see nothing in export)

[andresgongora]

You would have to unset ALL declared functions manually if not done like in 1. By wrapping all auxiliary function in a master function, their scope gets limited. I'm testing it on features/cleanup_status banch

[andresgongora]

After some tests, this can be omitted for now. Still, the script should avoid at all cost polluting the user's environment.