Net de fout gevonden, 't heeft te maken met variable scope (ik vermoede al zoiets):
Citaat:
E4) If I pipe the output of a command into `read variable', why doesn't
the output show up in $variable when the read command finishes?
This has to do with the parent-child relationship between Unix
processes. It affects all commands run in pipelines, not just
simple calls to `read'. For example, piping a command's output
into a `while' loop that repeatedly calls `read' will result in
the same behavior.
Each element of a pipeline runs in a separate process, a child of
the shell running the pipeline. A subprocess cannot affect its
parent's environment. When the `read' command sets the variable
to the input, that variable is set only in the subshell, not the
parent shell. When the subshell exits, the value of the variable
is lost.
En nu de oplossing:
Code:
counter=1
cat poempidoem.txt | while read line
do
echo $line >> poempidoemexploded/$counter.txt
if (echo $line | grep "^--" > /dev/null)
then
echo $counter $line
((counter=counter+1))
fi
done
De code in de if wordt dus niet meer in een subshell uitgevoerd.