The debugger probably contains enough configuration
hooks that you'll never have to modify it yourself. You may change the
behavior of debugger from within the debugger using its
O command, from the command line via the
PERLDB_OPTS environment variable, and by running
any preset commands stored in rc files.
The debugger's command-line history mechanism doesn't
provide command-line editing like many shells do: you can't retrieve
previous lines with
^p, or move to the beginning
of the line with
^a, although you can execute
previous lines with using the exclamation point syntax familiar to
shell users. However, if you install the
Term::ReadLine modules from CPAN, you will have
full editing capabilities similar to what GNU
If you have emacs installed on your system, it can interact with the Perl debugger to provide an integrated software development environment reminiscent of its interactions with C debuggers. Perl comes with a start file for making emacs act like a syntax-directed editor that understands (some of) Perl's syntax. Look in the emacs directory of the Perl source distribution. Users of vi should also look into vim (and gvim, the mousey and windy version) for coloring of Perl keywords.
A similar setup by one of us (Tom) for interacting with any vendor-shipped vi and the X11 window system is also available. This works similarly to the integrated multiwindow support that emacs ...