Georg Brandl [EMAIL PROTECTED] 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
Georg Brandl [EMAIL PROTECTED] writes:
Michael Hudson wrote:
Georg Brandl [EMAIL PROTECTED] writes:
The call to curses.setupterm() leaves my terminal in a bad state.
Hmm.
The reset program outputs:
Erase set to delete.
Kill set to control-U (^U).
Interrupt set to control-C (^C).
Michael Hudson wrote:
Georg Brandl [EMAIL PROTECTED] writes:
Michael Hudson wrote:
Georg Brandl [EMAIL PROTECTED] writes:
The call to curses.setupterm() leaves my terminal in a bad state.
Hmm.
The reset program outputs:
Erase set to delete.
Kill set to control-U (^U).
Interrupt
Georg Brandl [EMAIL PROTECTED] writes:
The call to curses.setupterm() leaves my terminal in a bad state.
Hmm.
The reset program outputs:
Erase set to delete.
Kill set to control-U (^U).
Interrupt set to control-C (^C).
It always says that :) (unless you've messed with stty, I guess)
Michael Hudson wrote:
Georg Brandl [EMAIL PROTECTED] writes:
The call to curses.setupterm() leaves my terminal in a bad state.
Hmm.
The reset program outputs:
Erase set to delete.
Kill set to control-U (^U).
Interrupt set to control-C (^C).
It always says that :) (unless you've
