idlwave: Commands Sent to the Shell
5.3 Commands Sent to the Shell
==============================
The IDLWAVE buffers and shell interact very closely. In addition to the
normal commands you enter at the ‘IDL>’ prompt, many other special
commands are sent to the shell, sometimes as a direct result of invoking
a key command, menu item, or toolbar button, but also automatically, as
part of the normal flow of information updates between the buffer and
shell.
The commands sent include ‘breakpoint’, ‘.step’ and other debug
commands (
Debugging IDL Programs), ‘.run’ and other compilation
statements (Compiling Programs), examination commands like
‘print’ and ‘help’ (Examining Variables), and other special
purpose commands designed to keep information on the running shell
current.
By default, much of this background shell input and output is hidden
from the user, but this is configurable. The custom variable
‘idlwave-abbrev-show-commands’ allows you to configure which commands
sent to the shell are shown there. For a related customization for
separating the output of _examine_ commands, see Examining
Variables.
-- User Option: idlwave-shell-show-commands (‘'(run misc breakpoint)’)
A list of command types to echo in the shell when sent. Possible
values are ‘run’ for ‘.run’, ‘.compile’ and other run commands,
‘misc’ for lesser used commands like ‘window’, ‘retall’,‘close’,
etc., ‘breakpoint’ for breakpoint setting and clearing commands,
and ‘debug’ for other debug, stepping, and continue commands. In
addition, if the variable is set to the single symbol
‘'everything’, all the copious shell input is displayed (which is
probably only useful for debugging purposes). N.B. For hidden
commands which produce output by side-effect, that output remains
hidden (e.g., stepping through a ‘print’ command). As a special
case, any error message in the output will be displayed (e.g.,
stepping to an error).
Info Catalog
idlwave: Using the Shell
idlwave: The IDLWAVE Shell
idlwave: Debugging IDL Programs