Eli Schwartz <eschwa...@archlinux.org> writes: > Why not just run bash -x script-name without the bash -l option and > without $BASH_ENV set? > > The first is implicitly true based on your stated command line. The > second doesn't seem like a high bar to set, and it's not exactly default > behavior... if you really do need $BASH_ENV can't you do the set -x at > the end of that file?
That's a good point, and I admit I've never studied out all of the logic of Bash init files; I assumed that it executed ~/.bashrc as a matter of course. So as long as I don't need the facilities in .bashrc for the script, then "BASH_ENV= bash ..." suffices. In regard to "can't you do the set -x at the end of that file", (1) it's inelegant and a PITA, and (2) it sauses sub-scripts to generate debugging output. Dale
