bash cli

[Todd Zullinger]

Stuart Murray-Smith wrote:
> Yes, it's difficult to describe, and that's prolly why I've
> struggled to Google it. If one completed a bash script with 'exit 0'
> and all ran well, nothing (or null) is sent to stdout. If a script
> passes a variable on to another executable, this is may not
> necessarily be sent to stdout, but there is something one can pass
> at cli time that does copy this/these var(s) to stdout to see what
> same script produces.

Put "set -x" near the top of the script or run it via sh -x.  As in:

sh -x /some/script/that/you/want/to/debug

Is that the sort of thing you're after?

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Eat dye and shit colours.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 542 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20070821/696a48b4/attachment-0002.bin