summaryrefslogtreecommitdiff
path: root/tests/sharness.sh
diff options
context:
space:
mode:
authorNick Kousu <nick@kousu.ca>2018-06-14 15:28:36 +0200
committerJason A. Donenfeld <Jason@zx2c4.com>2018-06-14 16:58:28 +0200
commit4a6fa5cbdf093d7873524fe566f58bca3761592e (patch)
tree4f0cb359b09ab8f7ce70662b5db239185bff2ead /tests/sharness.sh
parentfd2cbdacaed23c57b03cde19fe5eb6f910420855 (diff)
downloadpass-4a6fa5cbdf093d7873524fe566f58bca3761592e.tar.gz
pass-4a6fa5cbdf093d7873524fe566f58bca3761592e.tar.bz2
pass-4a6fa5cbdf093d7873524fe566f58bca3761592e.zip
Don't trap INT or TERM; they are redundant and can break `pass edit`.
Some EDITORs, notably Linux vi(1), which is the fallback default in pass, apparently send INT when they exit, and when pass is run under bash (which is also its default)--if you have /dev/shm/ available--bash catches this and cleans up your edited password file *before* it can be reencrypted and saved. This only happens with `pass edit`; none of the other commands combine tmpdir and $EDITOR.
Diffstat (limited to 'tests/sharness.sh')
0 files changed, 0 insertions, 0 deletions