Issue with (not) restoring original keypad mode on exit

[Paul Fertser]

Hi,

When an ncurses application that uses keypad mode is executing another such
application, the keypad mode gets reset after the child exits, so the
parent application gets wrong keycodes as it's still expecting keypad mode
to be active.

The particular issue I have is with mcabber (Jabber client) calling
(indirectly, via gpgme -> gpg2 -> gpg-agent) pinentry-curses to unlock a GPG
key, using TERM=screen. After pinentry-curses exits, the bindings are obviously
messed up. This doesn't happen with TERM=linux as it lacks smkx, rmkx
sequences.

I have no clue how to fix it properly, as there doesn't seem to be any way to
query the current keypad mode. Probably it would work just fine if screen
definition didn't include smkx, rmkx at all. Spent a whole day digging this...

TIA
-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:address@hidden