Re: Fw: Re: keypad & non-default terminal

[folkert]

>     Forgive me if this isn't the appropriate place in which to continue
> discussing this problem, as I don't believe the problem is a bug in ncurses.
>     I believe the problem with parsing the keystrokes is due to how things
> are set up on the client side, specifically with regards to terminal modes
> and buffering.
>     The client's terminal must be configured to be in raw mode. This is
> normally accomplished by calling the (n)curses raw(3) function, but that
> function only works on local terminals; it doesn't work across a socket.

It does :-)
The problem was that I had given the wrong terminal type to newterm. Now
that I "ask", on telnet-level, what terminal type the client has and act
upon that, since then cursor keys etc work fine.

Thanks for your help!
Much appreciated.