The obvious solution is to have the program IMMEDIATELY save its tty
settings on startup prior to ANY curses calls, and restore them when it
exits, after the curses exit has happened.

...or are the programs in question suffering from something more subtle?

Perhaps the old "Berkeley parochialisms" (subset 4:  tty settings:  "7E1
is how ALL the world talks.  ...isn't it?") are still here after all
these years and need to be discarded in favour of more ... um, "real
world" environmental settings (please don't take that as derogatory,
as it's simply an observation).


--
 _______Wizardry is dead._____ _____WHO: Greywolf (my nameplate even says so)
/ ___\ _ \ __\ V / \  / /__ \| | __/WHAT: UNIX System Mangler...er, Admin
\ \| |   < _| ` ' \ '` / \/ /|_| _/ WHERE: Autodesk, Inc.  3 Harbor Dr.
 \___|_|\_\__\|_|  \/\/ \__/___/_|  Sausalito, CA 94965 (415) 332-2344 x4219
	see also: gandalf@netcom.com