3 ms·
This is what I do, and just so others know: Realize that if your personal account's shell is pointed into the homebrew installation in /usr/local, and you impl
by mieko 10y ago
This is what I do, and just so others know:
Realize that if your personal account's shell is pointed into the homebrew installation in /usr/local, and you implode homebrew or wipe /usr/local, you won't be able to start a terminal until your shell is changed or the binary exists. Solving this without Terminal.app being able to launch is a minor annoyance.
- tambourine_man 10y agoThat is a very good point, thank you
- theonemind 10y agoThe proof of this is trivial, and left to the reader.
- RJIb8RBYxzAMX9u 10y agoRight, so have Terminal run this instead: #!/bin/sh for shell in \ /opt/local/bin/bash \ /bin/bash \ /bin/sh do [ -x "$shell" ] && exec "$shell" -l done echo >&2 "ERROR: No valid shell found!" read -r -s -n 1 -t 10 dummy exit 1
- QuercusMax 10y agoIf you are able to run a script with #!/bin/sh, and /bin/sh becomes un-executable during the execution of your script, you're definitely having a bad time. :D