On 04/28/2013 12:01 PM, todd....@gmail.com wrote: >> Read this thread for more details: >> >> https://lists.gnu.org/archive/html/help-bash/2013-04/msg00031.html >> >> >> >> In particular, that thread points out: >> >> http://mywiki.wooledge.org/BashFAQ/050 >>
> > Omitting the set -x from the original post was my error: > 1) I wouldn't live without it for debugging purposes. > 2) set x- creates a lot of "noise" on the screen the suites cannot live with. > > Is there no foundation for this request to make our lives bit more > comfortable? Did you not read the FAQ entry, which mentions that a DEBUG trap that collects $BASH_COMMAND (both bash extensions) exists as the nicest way to trace what your script did, and can be used in a way that doesn't interfere with the stdout/stderr that is already expected in your testsuite. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
