CODEWITHSUNDEEP
bashvariablespipe
jcalfee314
jcalfee314

Reputation: 4850

bash piping prevents global variable assignment

unset v
function f {
  v=1
}
f | cat
echo v=$v
f 
echo v=$v

Why does piping (to any command) prevent the first echo command from printing 1? The second echo prints 1. I'm using a bash shell. I can see this by copy/paste or by running this as a script.

Upvotes: 9

Views: 2602

Answers (1)

Paŭlo Ebermann
Paŭlo Ebermann

Reputation: 74800

All components of a pipeline (if more than one) are executed in a subshell, and their variable assignments do not persist to the main shell.

The reason for this is that bash does not support real multithreading (with concurrent access to variables), only subprocesses which run in parallel.

How to avoid this:

You have to do any variable assignments you want to retain in the main bash process (or find some way to transfer them there). The bash way of doing this would be not to use a pipe, but use process substitution instead:

f > >( cat )

Of course, this will not help if you need to do variable assignments in both processes of a pipe. Then you have to think of a better mechanism instead (maybe coprocesses, and output the variables somewhere?)

Upvotes: 15

Related Questions