<div dir="ltr">I typically use 'set' and put each of the switches on it's own line. My bash script template includes:<div><br></div><div> #!/bin/bash</div><div><br></div><div> #set -x</div><div> #set -v</div><div> set -a</div><div> set -e</div><div> set -u</div><div><br></div><div>Then I comment and uncomment as needed. </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 8, 2015 at 10:40 PM, David L. Anselmi <span dir="ltr"><<a href="mailto:anselmi@anselmi.us" target="_blank">anselmi@anselmi.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">David L. Willson wrote:<br>
><br>
> I use eu always, and x when I'm having problems.<br>
<br>
</span>Yes, that's good. u helps you catch typos in variable names (that otherwise just expand to nothing).<br>
<br>
If you think there might be times when e stops your script and it shouldn't, you can always catch<br>
the error return and do the right thing from there. If you don't know what will cause an error or<br>
you don't know what the right thing is then exiting (via the e) is probably your best choice.<br>
<br>
FWIW<br>
<br>
Dave<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br></div>