Korn Shell Programming by Example

Execution Trace

I find that the verbose option makes it difficult to locate the normal output lines because they are lost within all the extra displays. Come to think of it, I did ask for “verbose” output, didn't I?

The next debugging option not only leaves the bread crumbs through the woods, but it also leaves the type of bread, the baker, the expiration date, and the names of any animals that might have given it a nibble. (Another one over the top, no?) The idea is that it displays more information than just the command sequence.

Besides displaying the command before executing the command, you also might ask the Korn Shell to expand any wildcards and variables before displaying the command to be executed. This gives you the chance to understand ...