>> 	the arrow keys stop working in vi if i suspend it, run another
>> 	program (eg, vi or man, probably others), and then resume.
>
>I think the immediate workaround is not to use curses keypad() function
>(undef HAVE_CURSES_KEYPAD).  Nvi version of the function is different
>from that of curses.
>
>But, hmm...,
>I think the traditional curses had an exported function "tstp()",
>which does suspend and all the troublesome things about it
>in place of the userland programmer.
>
>What is the correct way to suspend a process with modern curses?
>__stop_signal_handler() does it, but it doesn't seem exported....

please note that it's not *just* being suspended that messes up vi.
if i suspend it and then resume, i'm fine.  it's only if the other
thing that i do in between also involves the "alternate" screen, which
for me is the difference between 'printf "\e[?47h"' and 'printf
"\e[?47l"' (in an xterm).  i dunno what that's really called.  maybe
it's actually a bug in curses...

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."