Script stops, although "set -e" was set afterward read

Asked Sep 06 '18 at 13:59

Active Sep 06 '18 at 15:17

Viewed 54 times

I have a script for a git post-receive hook

read oldrev newrev refname
set -e

echo DELETE
rm -rf *
echo DELETED
...

When I run the script, the ouput looks like this

remote: DELETE

But then the script stops. But when I remove the "set -e" or remove the "read" it works.

read oldrev newrev refname

echo DELETE
rm -rf *
echo DELETED
...

results to

remote: DELETE
remote: DELETED

set -e

echo DELETE
rm -rf *
echo DELETED

results to

remote: DELETE
remote: DELETED

I don't understand why it doesn't work.

Edit: Add output of the second and third code example

edited Sep 06 '18 at 15:17

asked Sep 06 '18 at 13:59

William M.

1

By "works", you mean files are removed and `DELETED` is output? – chepner Sep 06 '18 at 14:32
Yes, for the second and third code example the whole script runs. – William M. Sep 06 '18 at 15:16
Unless this is something really specific to Git hooks, I can't reproduce it with a simple example. I don't see how the `read` command could cause the later `rm` command to fail (which is the only thing that could explain your three results). – chepner Sep 06 '18 at 15:21
By the way, this is one more reason not to use `set -e` in the first place. – chepner Sep 06 '18 at 15:23
How else do you prevent the script from continuing when an error occurs? – William M. Sep 06 '18 at 16:19
Test for an error explicitly using `if ` – cdarke Sep 06 '18 at 18:09

0 Answers0