Erik Rose
Erik Rose
This comes in handy for sending it segments of very large compressed files.
It's really freaking hard to read the state of the keyboard without calling `curses.initscr().getch()`. Let's make it easier on people; I've had 2 requests about it. Here's one implementation, from...
Think about supporting 256-color palettes. If we do it, we should either be able to detect whether it's supported (via $TERM, or is there a cap we can check?) and/or...
Output on vt102 is a mess. See if it's my fault. ``` $$ERROR: blessings.tests:test_horizontal_location$ $bbedit +74 blessings/tests.py$ # test_horizontal_location$ eq_(t.stream.getvalue(), t.save + tparm(tigetstr('hpa'), 5) + t.restore) TypeError: tparm() argument 1...
Provide a way to test whether a formatter (like "green", "red_on_green", "bold", or "bold_underline_on_white") is valid so we can take them from the commandline without worrying about having a TypeError...
Apparently, `'\033[%sm]' % 39` and 49 clear the fg and bg color, respectively. I can't seem to find hide or hair of them on the terminfo man page, though. Figure...
Right now, we catch bad format specifiers (`blue_on_greeeeeen`) when they're used to actually wrap something. Can we catch them sooner while still providing access to all tty caps? Or perhaps...
The link on `[Bazel Query How-To](https://query/guide)` is broken.
Maybe stick [references to] the toolset functions within an outer function and return locals() from it, rather than writing out a big dict like https://github.com/peter17/mediawiki-parser/commit/19d8ad32e577ab2c9a35b65a1349133ff33f3b61#L0L26.