Jeff Quast

I think Erik got his house. Now i'm the busy one, looking for a place myself. I've been piecemealing 1 large pull request as individual pulls, working towards keyboard again....

I'll take another look soon... its not that travis runs in a pty, but that another pty can be spawned using pty.fork and behave the way I expect it to....

I've resolved the pty issue, pull #42 is fully resolved. Once Erik reviews & merges this I'll be able to build upon the fixes and improved test infrastructure and submit...

keyboard support is implemented in my fork, https://github.com/jquast/blessed/ -- appreciate any feedback before it goes to pypi.

This is resolved in 'blessed-integration' branch.

The fork `blessed` contains full keyboard (even with windows!), with plenty of fun examples and successful use in downstream 3rd party apps, please enjoy. https://blessed.readthedocs.io/en/latest/keyboard.html 

I agree. I think this is only a problem for 'screen', so far as I can tell. They can be fixed by assigning an anonymous function for this case. ```...

this is fixed as you recommend, "internally workaround this problem transparently", in a fork if you wish to need it, https://pypi.python.org/pypi/blessed

I definitely tried to contribute all of my fixes and enhancements, beginning last year. The pull requests were mostly ignored/stalled -- Look in "closed" pull requests in this project and...

I'm afraid I can't do that. For example, this change cannot be tested without \@as_subprocess -- as your first test case that tests xterm-256color causes all subsequent tests to be...