From 0e0e391fa3954a2583fe464504b86983a22d2577 Mon Sep 17 00:00:00 2001 From: R David Murray Date: Tue, 15 Apr 2014 20:25:18 -0400 Subject: [PATCH] #20874: update tutorial wording: sophisticated line editing is now standard. Patch by Rafael Mejia. --- Doc/tutorial/interpreter.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/Doc/tutorial/interpreter.rst b/Doc/tutorial/interpreter.rst index 8e8395a3496..398ed72209b 100644 --- a/Doc/tutorial/interpreter.rst +++ b/Doc/tutorial/interpreter.rst @@ -35,10 +35,9 @@ Windows) at the primary prompt causes the interpreter to exit with a zero exit status. If that doesn't work, you can exit the interpreter by typing the following command: ``quit()``. -The interpreter's line-editing features usually aren't very sophisticated. On -Unix, whoever installed the interpreter may have enabled support for the GNU -readline library, which adds more elaborate interactive editing and history -features. Perhaps the quickest check to see whether command line editing is +The interpreter's line-editing features include interactive editing, history +substitution and code completion on systems that support readline. +Perhaps the quickest check to see whether command line editing is supported is typing Control-P to the first Python prompt you get. If it beeps, you have command line editing; see Appendix :ref:`tut-interacting` for an introduction to the keys. If nothing appears to happen, or if ``^P`` is echoed,