summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Kluyver <takowl@gmail.com>2013-09-25 18:52:11 -0700
committerThomas Kluyver <takowl@gmail.com>2013-09-25 18:52:11 -0700
commit46b457f753cc5976d9f6094cfc825b2b20f4acd9 (patch)
tree8aa188f00d4326d2f7caa4ac1500439cc25c6c6f
parent38a0899cf0c7dda206fc429516a770f97703160d (diff)
downloadpexpect-46b457f753cc5976d9f6094cfc825b2b20f4acd9.tar.gz
Fix some spelling mistakes
-rw-r--r--pexpect/__init__.py10
1 files changed, 5 insertions, 5 deletions
diff --git a/pexpect/__init__.py b/pexpect/__init__.py
index 8af06ff..7b69d3c 100644
--- a/pexpect/__init__.py
+++ b/pexpect/__init__.py
@@ -336,14 +336,14 @@ class spawn(object):
output are read back from the child. This feature is useful in
conjunction with searchwindowsize.
- The searchwindowsize attribute sets the how far back in the incomming
+ The searchwindowsize attribute sets the how far back in the incoming
seach buffer Pexpect will search for pattern matches. Every time
Pexpect reads some data from the child it will append the data to the
- incomming buffer. The default is to search from the beginning of the
- imcomming buffer each time new data is read from the child. But this is
+ incoming buffer. The default is to search from the beginning of the
+ incoming buffer each time new data is read from the child. But this is
very inefficient if you are running a command that generates a large
- amount of data where you want to match The searchwindowsize does not
- effect the size of the incomming data buffer. You will still have
+ amount of data where you want to match. The searchwindowsize does not
+ affect the size of the incoming data buffer. You will still have
access to the full buffer after expect() returns.
The logfile member turns on or off logging. All input and output will