Re: "exit" doesn't work from inside of PIPED read block

Bob Proulx wrote: >>> Why are you using the -p option? >>> >>> >> To prevent possible side effects from inheriting shell functions from >> current environment, SHELLOPTS, any settings in $ENV, etc. Why would I >> want to have all that crap in my environment if my goal is to test >> exact

Re: "exit" doesn't work from inside of PIPED read block

Blaine Simpson wrote: > Bob Proulx wrote: > > Please keep the mailing list in the CC so that others may participate > > in the discussion and enable it to be available in the archives. Grr... This means please do a list reply in your mailer or if list reply is not available then use the followup

Re: "exit" doesn't work from inside of PIPED read block

Please keep the mailing list in the CC so that others may participate in the discussion and enable it to be available in the archives. > #!/bin/bash -p Why are you using the -p option? > echo $$ > cat /tmp/atf | while read; do echo $$; exit 3; done In both cases the $$ is expanded by the shell

Re: "exit" doesn't work from inside of PIPED read block

Blaine Simpson wrote: > "exit" doesn't exit the current shell when inside of PIPED read blocks, > yet everything works find if the input comes from "redirection". This is because pipes operate in subshells and the exit applies to the subshell. Please see the bash FAQ question E4 for mor