From: Mark-Jason Dominus <mjd@plover.com>
Date: Sun, 1 Apr 2001 14:25:11 +0000 (-0400)
Subject: PATCH 5.6.0 (perldebug.pod)
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=e00d725bc363e74167fef81bb7b844d680d260d3;p=p5sagit%2Fp5-mst-13.2.git

PATCH 5.6.0 (perldebug.pod)
Message-ID: <20010401182511.9247.qmail@plover.com>

p4raw-id: //depot/perl@9505
---

diff --git a/pod/perldebug.pod b/pod/perldebug.pod
index 01f35e1..0aff91a 100644
--- a/pod/perldebug.pod
+++ b/pod/perldebug.pod
@@ -465,6 +465,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
 
@@ -600,9 +602,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: