Re: [PATCH] the the double double word word fix fix

[perl5.git] / pod / perldebug.pod

diff --git a/pod/perldebug.pod b/pod/perldebug.pod
index c8ef60f..2133fcf 100644 (file)
--- a/pod/perldebug.pod
+++ b/pod/perldebug.pod
@@ -82,7 +82,7 @@ recursively, unlike the real C<print> function in Perl.
 See L<Dumpvalue> if you'd like to do this yourself.
 
 The output format is governed by multiple options described under
-L<"Options">.
+L<"Configurable Options">.
 
 =item V [pkg [vars]]
 
@@ -182,10 +182,12 @@ accessible.
 =item /pattern/
 
 Search forwards for pattern (a Perl regex); final / is optional.
+The search is case-insensitive by default.
 
 =item ?pattern?
 
 Search backwards for pattern; final ? is optional.
+The search is case-insensitive by default.
 
 =item L
 
@@ -308,8 +310,8 @@ For historical reasons, the C<=value> is optional, but defaults to
 1 only where it is safe to do so--that is, mostly for Boolean
 options.  It is always better to assign a specific value using C<=>.
 The C<option> can be abbreviated, but for clarity probably should
-not be.  Several options can be set together.  See L<"Options"> for
-a list of these.
+not be.  Several options can be set together.  See L<"Configurable Options"> 
+for a list of these.
 
 =item < ? 
 
@@ -342,7 +344,7 @@ missing, all actions are wiped out!
 
 Adds an action (Perl command) to happen after the prompt when you've
 just given a command to return to executing the script.  A multi-line
-command may be entered by slackbashing the newlines.
+command may be entered by backslashing the newlines.
 
 =item { ?
 
@@ -385,6 +387,11 @@ their C<$ENV{SHELL}> variable) will be used, which can interfere
 with proper interpretation of exit status or signal and coredump
 information.
 
+=item @ file
+
+Read and execute debugger commands from I<file>.  I<file> may itself contain
+C<@> commands.
+
 =item H -number
 
 Display last n commands.  Only commands longer than one character are
@@ -465,6 +472,8 @@ working example of something along the lines of:
 
 The debugger has numerous options settable using the C<O> command,
 either interactively or from the environment or an rc file.
+(./.perldb or ~/.perldb under Unix.)
+
 
 =over 12
 
@@ -553,6 +562,10 @@ next option:
 Length to truncate the argument list when the C<frame> option's
 bit 4 is set.
 
+=item C<windowSize>
+
+Change the size of code list window (default is 10 lines).
+
 =back
 
 The following options affect what happens with C<V>, C<X>, and C<x>
@@ -600,9 +613,11 @@ include lexicals in a module's file scope, or lost in closures.
 
 =back
 
-During startup, options are initialized from C<$ENV{PERLDB_OPTS}>.
-You may place the initialization options C<TTY>, C<noTTY>,
-C<ReadLine>, and C<NonStop> there.
+After the rc file is read, the debugger reads the C<$ENV{PERLDB_OPTS}>
+environment variable and parses this as the remainder of a `O ...'
+line as one might enter at the debugger prompt.  You may place the
+initialization options C<TTY>, C<noTTY>, C<ReadLine>, and C<NonStop>
+there.
 
 If your rc file contains:
 
@@ -767,6 +782,11 @@ Breakable lines are marked with C<:>.  Lines with breakpoints are
 marked by C<b> and those with actions by C<a>.  The line that's
 about to be executed is marked by C<< ==> >>.
 
+Please be aware that code in debugger listings may not look the same
+as your original source code.  Line directives and external source
+filters can alter the code before Perl sees it, causing code to move
+from its original positions or take on entirely different forms.
+
 =item Frame listing
 
 When the C<frame> option is set, the debugger would print entered (and
@@ -901,12 +921,12 @@ interpret the information in that profile.
 
 =head1 Debugging regular expressions
 
-C<use re 'debug'> enables you to see the gory details of how the
-Perl regular expression engine works.  In order to understand this
-typically voluminous output, one must not only have some idea about
-about how regular expression matching works in general, but also
-know how Perl's regular expressions are internally compiled into
-an automaton.  These matters are explored in some detail in
+C<use re 'debug'> enables you to see the gory details of how the Perl
+regular expression engine works. In order to understand this typically
+voluminous output, one must not only have some idea about how regular
+expression matching works in general, but also know how Perl's regular
+expressions are internally compiled into an automaton. These matters
+are explored in some detail in
 L<perldebguts/"Debugging regular expressions">.
 
 =head1 Debugging memory usage