Fix issues found by codespell

Author: sebastinas

.github/workflows/lint.yaml

@@ -25,4 +25,4 @@ jobs:
     - uses: codespell-project/actions-codespell@master
       with:
         skip: '*.po'
-        ignore_words_list: ba,te,deltion
+        ignore_words_list: te,ot

curtsies/formatstring.py

@@ -461,7 +461,7 @@ def join(self, iterable):
     # TODO make this split work like str.split
     def split(self, sep=None, maxsplit=None, regex=False):
         # type: (Text, int, bool) -> List[FmtStr]
-        """Split based on seperator, optionally using a regex.
+        """Split based on separator, optionally using a regex.
 
         Capture groups are ignored in regex, the whole pattern is matched
         and used to split the original FmtStr."""
@@ -597,7 +597,7 @@ def __mul__(self, other):
             return sum([self for _ in range(other)], FmtStr())
         raise TypeError("Can't multiply those")
 
-    # TODO ensure emtpy FmtStr isn't a problem
+    # TODO ensure empty FmtStr isn't a problem
 
     @property
     def shared_atts(self):

curtsies/input.py

@@ -333,7 +333,7 @@ def threadsafe_event_trigger(self, event_type):
 
         Returned callback function will create an event of type event_type
         which will interrupt an event request if one
-        is concurrently occuring, otherwise adding the event to a queue
+        is concurrently occurring, otherwise adding the event to a queue
         that will be checked on the next event request."""
         readfd, writefd = os.pipe()
         self.readers.append(readfd)

curtsies/window.py

@@ -152,7 +152,7 @@ def for_stdout(s):
 
 
 class FullscreenWindow(BaseWindow):
-    """2D-text rendering window that dissappears when its context is left
+    """2D-text rendering window that disappears when its context is left
 
     FullscreenWindow will only render arrays the size of the terminal
     or smaller, and leaves no trace on exit (like top or vim). It never
@@ -280,7 +280,7 @@ def __init__(
                 on leaving context
             hide_cursor (bool): Hides cursor while in context
             extra_bytes_callback (f(bytes) -> None): Will be called with extra
-                bytes inadvertantly read in get_cursor_position(). If not
+                bytes inadvertently read in get_cursor_position(). If not
                 provided, a ValueError will be raised when this occurs.
         """
         BaseWindow.__init__(self, out_stream=out_stream, hide_cursor=hide_cursor)
@@ -337,7 +337,7 @@ def retrying_read():
                     c = in_stream.read(1)
                     if c == "":
                         raise ValueError(
-                            "Stream should be blocking - should't"
+                            "Stream should be blocking - shouldn't"
                             " return ''. Returned %r so far",
                             (resp,),
                         )

docs/FSArray.rst

@@ -56,7 +56,7 @@ An array like the above might be repeatedly constructed and rendered with a :py:
 
 Slicing works like it does with a :py:class:`~curtsies.FmtStr`, but in two dimensions.
 :py:class:`~curtsies.FSArray` are *mutable*, so array assignment syntax can be used for natural
-compositing as in the above exaple.
+compositing as in the above example.
 
 If you're dealing with terminal output, the *width* of a string becomes more
 important than it's *length* (see :ref:`len-vs-width`).

docs/Input.rst

@@ -26,7 +26,7 @@ and can be acted upon.
 Since it's iterable, ``next()`` can be used to wait for a single event.
 :py:meth:`~curtsies.Input.send` works like ``next()`` but takes a timeout
 in seconds, which if reached will cause None to be returned signalling
-that no keypress or other event occured within the timeout.
+that no keypress or other event occurred within the timeout.
 
 Key events are unicode strings, but sometimes event objects
 (see :class:`~curtsies.events.Event`) are returned instead.

docs/ansi.py

@@ -124,7 +124,7 @@ def _colorize_block_contents(self, block):
         last_end = 0
         # iterate over all color codes
         for match in COLOR_PATTERN.finditer(raw):
-            # add any text preceeding this match
+            # add any text preceding this match
             head = raw[last_end : match.start()]
             self._add_text(head)
             # update the match end

docs/gameloop.rst

@@ -1,7 +1,7 @@
 Gameloop Example
 ^^^^^^^^^^^^^^^^
 
-Use scheduled events for realtime interative programs:
+Use scheduled events for realtime interactive programs:
 
 .. literalinclude:: ../examples/fps.py
 

notes/notesfromdarius.txt

@@ -12,7 +12,7 @@ read this: http://www.cs.utexas.edu/~wcook/Drafts/2009/essay.pdf
 
   (erlang was also cool like that, maybe look at it again)
 
-played at all with sounds fairly diff, cool in that syate very explicty very cool
+played at all with sounds fairly diff, cool in that syate very explicitly very cool
 
  i assume you've seen how objc- does it?
 
@@ -22,7 +22,7 @@ I was guessing it would use font, but I was wrong
 
 or font or something
 
-check out Darius's halp - for editor <-> repl interaction without the repl
+check out Darius's help - for editor <-> repl interaction without the repl
 
 I going to get some food
 
@@ -33,10 +33,10 @@ this could also be pass this message
 
 right now it's not realtime it blocks on getting an event, and has no timer events or  - butit'd be nice to change
 
-I thoguht the simpler model was perfect for a repl - wait until user does somethign - but code can do anything
+I thoguht the simpler model was perfect for a repl - wait until user does something - but code can do anything
 which way?
 
-I guess I don't wan tto deal with threads unless each thread is an event driven loop <- I just don't hvae this yet
+I guess I don't want tto deal with threads unless each thread is an event driven loop <- I just don't have this yet
 
 right now it's a single thread of execution
 
@@ -51,7 +51,7 @@ run code
 run code
 oh code wants to read on stdin - so this is a greenet, suspend execution and
 
-the realization I had was that in bptuhon-curtiess I 'm also emulating the terminal - I'm responsible for colelcting that the user hit a key at *any* time, not jsut during input
+the realization I had was that in bptuhon-curtiess I 'm also emulating the terminal - I'm responsible for colelcting that the user hit a key at *any* time, not just during input
 
 so it really feels like an evented system? - at least queues and messaging and things
 
@@ -90,8 +90,8 @@ could you only have i
 
 deeplly immutable - E
 not obvious what this does
-then it's a boolean thing, so presence is enought
-shoudl be documentation of that
+then it's a boolean thing, so presence is enough
+should be documentation of that
 
 self.atts is a dictionary of {fg:blue, bg:red, bold:Trueo
 
@@ -101,7 +101,7 @@ I'm actually paying lea A. (hs'er) to make a logo! So if I ha
 
 Also if bpython starts to use this as ath main thing, I'lll need to work on cleanign it up.
 
-I guess so I don't have release things set up - I could give you github comit access for this and just put it on another brnach for now?
+I guess so I don't have release things set up - I could give you github commit access for this and just put it on another branch for now?
 
 git pull upstream
 
@@ -110,11 +110,11 @@ the readme is the only docs right now
 
 mostly tests
 
-I wrote the whole thing tried to do it clearly, then had performnace problems and went 
+I wrote the whole thing tried to do it clearly, then had performance problems and went 
 
 just python slice bookkeeping
 
-it's poorly named, it doens't accomplish that - it's just 
+it's poorly named, it doesn't accomplish that - it's just 
 
 asdf[1:] 
 normalize_slice(4, slice(1, None, None)) -> slice(1, 4, 1)
@@ -149,7 +149,7 @@ meaning that sequence isn't recognizd or isn't valid
 
 this depends on every input having 
 
-if ab is passed it assumes it must have alrady been called with a
+if ab is passed it assumes it must have already been called with a
 
 
     ther'e no speed concertn, we could assert that too

tests/test_fmtstr.py

@@ -347,7 +347,7 @@ def test_slice(self):
         self.assertEqual(s[1:], fmtstr("mp") + " ")
         self.assertEqual(blue("a\nb")[0:1], blue("a"))
 
-        # considering changing behavior so that this doens't work
+        # considering changing behavior so that this doesn't work
         # self.assertEqual(fmtstr('Hi!', 'blue')[15:18], fmtstr('', 'blue'))