When trying to open a document with VI editor, getting the following error..
E558: Terminal entry not found in terminfo
'vt100' not known. Available builtin terminals are:
builtin_gui
builtin_riscos
builtin_amiga
builtin_beos-ansi
builtin_ansi
builtin_pcansi
builtin_win32
builtin_vt320
builtin_vt52
builtin_xterm
builtin_iris-ansi
builtin_debug
builtin_dumb
defaulting to 'ansi'
What might be the possible cause and how to resolve this issue..??
What "vi" are you using ? on what Solaris distribution ?
Am using VIM - Vi IMproved version 6.3 on solaris SunOS 5.10
Did i answer your queries correctly ? If not kindly let me know the commands to check it.
Vim isn't part of Solaris 10. Where did you get it ? Was it properly installed ?
env >>my_env.txt
check how your terminal is set:
echo $TERM
echo $DISPLAY
Why am I having problems with terminfo/curses?
Terminator has its own terminfo file. This is regrettably necessary because of Terminator's unconventional approach to handling wide lines with a horizontal scrollbar rather than by wrapping them. The file will be installed under ~/.terminfo the first time you run Terminator. If you used an installer that runs as root and can write to the system-wide terminfo directory (currently just the Linux installer), the terminfo file will be installed system-wide at install time.
If you run Terminator itself as root and the terminfo file has not been installed in the system-wide terminfo directory, it will be installed at that point.
If the terminfo file isn't available, the most common warnings you'll see are this one from programs such as less(1):
WARNING: terminal is not fully functional
- (press RETURN)
and this one, from vim(1):
E558: Terminal entry not found in terminfo
'terminator' not known. Available builtin terminals are:
builtin_riscos
builtin_amiga
builtin_beos-ansi
builtin_ansi
builtin_pcansi
builtin_win32
builtin_vt320
builtin_vt52
builtin_xterm
builtin_iris-ansi
builtin_debug
builtin_dumb
defaulting to 'ansi'
If you think you have the correct terminfo available but you're still having problems, the next thing to check is that you're actually using Terminator's terminfo. For example, if your problem is with your shell, check that echo $TERM says "terminator", and if your problem is with Vim, check that :se term says "term=terminator".
Although Terminator sets the TERM environment variable to "terminator" for you, your shell's profile may be setting it to an incorrect value. Also, if you're logging in to a remote machine, the value of TERM may not be correctly transferred. It's always worth checking as described in the previous paragraph. The correct fix is to change your profile so it doesn't override TERM, and to use protocols like SSH which transfer your terminal type. You definitely shouldn't force TERM to be "terminator" (or any other value) in your profile: that's how you get into this kind of trouble.
Incredible, the text you pasted from somewhere doesn't help and is a different issue anyway. The OP is using vt100 as TERM, not terminator.
vt100 is a very common/basic termcap/terminfo entry while terminator is definitely not.
We don't know what physical terminal or terminal emulator is in use. It is pretty unlikely to be a vt100 .
Tempting to set TERM to vt320 and see if it works.
TERM=vt320;export TERM
vim filename
But it is pretty likely to be vt100 compatible. The main issue is vim not being properly installed, i.e. some required package wasn't installed. It should work whatever correct TERM is set.
Setting TERM to vt320 should work as a workaround though given the error message.
TERM=vt320 vim filename
is a simpler and safer way to try it.
I agree jlliagre. We don't know what the next command will be.
The issue with vt100/vt320 is function keys colours etc. The base control sequences should still work.
Btw. The real vt100 was a quality product and a refreshing break from green screens.