Redirecting Output

You can redirect the output of most Prism commands to a file by including an "at" sign (@) followed by the name of the file on the command line. For example,

where @ where.output

puts the output of a where command (a stack trace) into the file where.output, in your current working directory within Prism.

You can also redirect output of a command to a window by using the syntax on window, where window can be:

• command (abbreviated com) - This sends output to the command window; this is the default.

• dedicated (abbreviated ded) - This sends output to a window dedicated to output for this command. If you subsequently issue the same command (no matter what its arguments are) and specify that output is to be sent to the dedicated window, this window will be updated. For example,

list on ded

displays the output of the list command in a dedicated window. (Some commands that have equivalent menu selections display their output in the standard window for the menu selection.)

• snapshot (abbreviated sna) - This creates a window that provides a snapshot of the output. If you subsequently issue the same command and specify that output is to be sent to the snapshot window, Prism creates a separate window for the new output. The time each window was created is shown in its title. Snapshot windows let you save and compare outputs.

You can also make up your own name for the window; the name appears in the title of the window. This is useful if you want a particular label for a window. For example, if you were doing a stack trace at line 22, you could issue this command:

where on line22

to label the window with the location of the stack trace.

The commands whose output you cannot redirect are run, edit, make, and sh.

Although the run command cannot be redirected using on or @, run can be redirected using > and other shell redirections.