From: Bram Date: Sun, 31 May 2009 15:20:45 +0000 (+0200) Subject: Clarify perldebug documentation X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=3244086bce52e956e04c61b12eb7b67fc1041d8b;p=p5sagit%2Fp5-mst-13.2.git Clarify perldebug documentation Mention what happens without Readline support. --- diff --git a/pod/perldebug.pod b/pod/perldebug.pod index 2529901..3ba73e8 100644 --- a/pod/perldebug.pod +++ b/pod/perldebug.pod @@ -1056,11 +1056,12 @@ Note that any variables and functions that are not documented in this document (or in L) are considered for internal use only, and as such are subject to change without notice. -=head2 Readline Support +=head2 Readline Support / History in the debugger As shipped, the only command-line history supplied is a simplistic one that checks for leading exclamation points. However, if you install -the Term::ReadKey and Term::ReadLine modules from CPAN, you will +the Term::ReadKey and Term::ReadLine modules from CPAN (such as +Term::ReadLine::Gnu, Term::ReadLine::Perl, ...) you will have full editing capabilities much like GNU I(3) provides. Look for these in the F directory on CPAN. These do not support normal B command-line editing, however. @@ -1069,6 +1070,9 @@ A rudimentary command-line completion is also available. Unfortunately, the names of lexical variables are not available for completion. +Without Readline support you may see the symbols "^[[A", "^[[C", "^[[B", +"^[[D"", "^H", ... when using the arrow keys and/or the backspace key. + =head2 Editor Support for Debugging If you have the FSF's version of B installed on your system,