|Powered by QM on a Rpi server|
QM assumes that telnet connections start with binary mode disabled. If your terminal emulator works in binary mode but does not send the related telnet negotiation parameter, the nul characters that appear after every newline will be treated as data. The solution is either to turn off binary mode in the emulator or to upgrade to an emulator that supports binary mode negotiation.
Some terminals (e.g. Wyse 50 and Wyse 60) send the same character for the backspace key and the cursor left key. QM is unable to distinguish these and may interpret the backspace as a cursor left or vice versa depending on how the input data is being processed. If possible, either use a different terminal type or modify the code sent by the emulator for cursor left (and the corresponding terminfo entry) to something different. If this is not possible, deleting the terminfo definition for the cursor left key (kcub1) will ensure that the key is always interpretted as a backspace.
QM uses the terminfo library to identify control sequences sent by terminals when special keys are pressed. The usual reason for incorrect recognition of cursor keys is that the wrong terminal type has been selected. The standard Microsoft telnet emulator provided with Windows used to use a vt100 emulation. Later versions are vt220 emulation.
Alternatively, some vt100 terminal emulators have an option to send variations of the cursor key codes.
In either case, the problem is almost certainly that your terminal emulator does not match the terminal type selected using the TERM command.
The standard Microsoft telnet emulator provided with later versions of Windows does not recognise the function keys. You will need to find an alternative terminal emulator if you need to use the function keys.
00017: Terminal Support