For those that have experience writing text-based ncurses apps in 6.2.1,
could you explain why I currently have to set my TERM=qnx and emulate “QNX
4” terminal on my PC? Every other terminal that I tried horribly screws up
the colors or the line drawing output of ncurses. I’ve tried all of the
“ansi” and “qansi” terms, the VTxxx family, etc. The only one that seems to
work more or less correctly is term type “qnx”.
Thanks in advance,
Jason
Some (most?) of the terminal definitions shipped with QNX are broken.
Then the console driver itself makes it even worse by not handling them
properly. And then some of the terminal types are unsuitable for your
job to begin with (don’t have pseudographics or color or both).
My (limited) experience with ncurses suggested that xterm and vt100 are
the most portable/reliable emulations. I did not use neither color nor
pseudographics though.
You can improve results somewhat by borrowing terminfo database from
some x86 Unix (linix, solaris, SCO should be fine).
– igor
Jason Farque’ wrote:
For those that have experience writing text-based ncurses apps in 6.2.1,
could you explain why I currently have to set my TERM=qnx and emulate “QNX
4” terminal on my PC? Every other terminal that I tried horribly screws up
the colors or the line drawing output of ncurses. I’ve tried all of the
“ansi” and “qansi” terms, the VTxxx family, etc. The only one that seems to
work more or less correctly is term type “qnx”.Thanks in advance,
Jason