Georg Brandl <g.brandl-nospam at gmx.net> writes: >> Well, this still has the faint whiff of impossibility about it. Are >> you sure it's setupterm() that's doing the damage? Can you reproduce >> interactively? > > Yep. > Alone, the setupterm call [curses.setupterm(sys.__stdout__.fileno())] does > nothing remarkable, but when it is done inside of curses.initscr() / curses.endwin() > the terminal is not restored properly. Ah! That does indeed make some small amount of sense. > If setupterm() is to be tested, I think it should be executed before initscr(). Sounds good. What are you waiting for? :) Cheers, mwh -- <etrepum> Jokes around here tend to get followed by implementations. -- from Twisted.Quotes
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4