Commit 0e0e391f authored by R David Murray's avatar R David Murray

#20874: update tutorial wording: sophisticated line editing is now standard.

Patch by Rafael Mejia.
parent 65425b4b
...@@ -35,10 +35,9 @@ Windows) at the primary prompt causes the interpreter to exit with a zero exit ...@@ -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 status. If that doesn't work, you can exit the interpreter by typing the
following command: ``quit()``. following command: ``quit()``.
The interpreter's line-editing features usually aren't very sophisticated. On The interpreter's line-editing features include interactive editing, history
Unix, whoever installed the interpreter may have enabled support for the GNU substitution and code completion on systems that support readline.
readline library, which adds more elaborate interactive editing and history Perhaps the quickest check to see whether command line editing is
features. 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, 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 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, introduction to the keys. If nothing appears to happen, or if ``^P`` is echoed,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment