Hi All,
I have had to go and build a new hard drive from scratch because I had
to change to a larger HD. In doing so I have developed a new problem
when trying to start vedit sessions. I now have the following returned
“term_load error. No such file or directory”. This is an untrue
statement because I’m in the directory when starting vedit. If I do a
‘more filename’ I get “WARNING: terminal is not fully functional”.
This is a QNX4.25 system on a 4GB drive. The TERM value is qnx
(TERM=qnx). It looks like I have some sort of terminal problem but I
have never seen this one before. The setting in my sysinit file for
tinit is 'tinit -T /dev/con* -t /dev/con1 &"
Anyone got any ideas how I find or correct this problem.
John
Previously, John Parsons wrote in qdn.public.qnx4:
Hi All,
I have had to go and build a new hard drive from scratch because I had
to change to a larger HD. In doing so I have developed a new problem
when trying to start vedit sessions. I now have the following returned
“term_load error. No such file or directory”. This is an untrue
statement because I’m in the directory when starting vedit. If I do a
‘more filename’ I get “WARNING: terminal is not fully functional”.
This is a QNX4.25 system on a 4GB drive. The TERM value is qnx
(TERM=qnx). It looks like I have some sort of terminal problem but I
have never seen this one before. The setting in my sysinit file for
tinit is 'tinit -T /dev/con* -t /dev/con1 &"
Anyone got any ideas how I find or correct this problem.
One guess - terminfo is a very intrusive creature that tries to
locally cache terminal information for each user under circumstances
that I have never characterized. It creates a directory, .terminfo,
in your home directory, and all programs are then directed to use that
prior to searching the system terminfo directory. The entries in
…terminfo come from outer space, and don’t necessarily represent the
capabilities of the terminal.
The fix (if this is your problem) is to erase .terminfo in you home
directory entirely. Put an rm -rf ~/.terminfo into your .profile if
it keeps coming back.
Cheers,
Andrew