summaryrefslogtreecommitdiff
path: root/docs/features/embedded_python_shells.rst
diff options
context:
space:
mode:
authorKevin Van Brunt <kmvanbrunt@gmail.com>2020-02-13 13:39:53 -0500
committerKevin Van Brunt <kmvanbrunt@gmail.com>2020-02-13 13:39:53 -0500
commit41019de4b55f42d17149c29d380358dc38347948 (patch)
tree896f769ab1d919132b51ee0dbf7006cf07f87961 /docs/features/embedded_python_shells.rst
parentc3e3c1c595d65ec4c5fa2c9dac88ffa30cf4738e (diff)
downloadcmd2-git-41019de4b55f42d17149c29d380358dc38347948.tar.gz
Removed dash from 'tab complete' string
Diffstat (limited to 'docs/features/embedded_python_shells.rst')
-rw-r--r--docs/features/embedded_python_shells.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/features/embedded_python_shells.rst b/docs/features/embedded_python_shells.rst
index 68377876..70765b21 100644
--- a/docs/features/embedded_python_shells.rst
+++ b/docs/features/embedded_python_shells.rst
@@ -67,7 +67,7 @@ code directory for an example of how to achieve this in your own applications.
Using ``py`` to run scripts directly is considered deprecated. The newer
``run_pyscript`` command is superior for doing this in two primary ways:
-- it supports tab-completion of file system paths
+- it supports tab completion of file system paths
- it has the ability to pass command-line arguments to the scripts invoked
There are no disadvantages to using ``run_pyscript`` as opposed to ``py