For simonw/museums#32 I wanted to have certain lines in my Bash script ignore any errors: lines that used sqlite-utils to add columns and configure FTS, but that might fail with an error if the column already existed or FTS had already been configured.
This tip on StackOverflow lead me to the following recipe:
\n#!/bin/bash\nset -euo pipefail\n\nyaml-to-sqlite browse.db museums museums.yaml --pk=id\npython annotate_nominatum.py browse.db\npython annotate_timestamps.py\n# Ignore errors in following block until set -e:\nset +e\nsqlite-utils add-column browse.db museums country 2>/dev/null\nsqlite3 browse.db < set-country.sql\nsqlite-utils disable-fts browse.db museums 2>/dev/null\nsqlite-utils enable-fts browse.db museums \\\n name description country osm_city \\\n --tokenize porter --create-triggers 2>/dev/null\nset -eEverything between the set +e and the set -e lines can now error without the Bash script itself failing.
The failing lines were still showing a bunch of Python tracebacks. I fixed that by redirecting their standard error output to /dev/null like this:
sqlite-utils disable-fts browse.db museums 2>/dev/null