summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorR David Murray <rdmurray@bitdance.com>2014-04-16 00:25:18 (GMT)
committerR David Murray <rdmurray@bitdance.com>2014-04-16 00:25:18 (GMT)
commit0e0e391fa3954a2583fe464504b86983a22d2577 (patch)
treecce5dda53c374058a8f463f5eb03373014b3b13d /Doc
parent65425b4bc6499bcbdf99ff1b82a02d8112359542 (diff)
downloadcpython-0e0e391fa3954a2583fe464504b86983a22d2577.zip
cpython-0e0e391fa3954a2583fe464504b86983a22d2577.tar.gz
cpython-0e0e391fa3954a2583fe464504b86983a22d2577.tar.bz2
#20874: update tutorial wording: sophisticated line editing is now standard.
Patch by Rafael Mejia.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/tutorial/interpreter.rst7
1 files changed, 3 insertions, 4 deletions
diff --git a/Doc/tutorial/interpreter.rst b/Doc/tutorial/interpreter.rst
index 8e8395a..398ed72 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,