topic Edit file in Operating System - Linux

Edit file

peterchu — Fri, 26 Aug 2005 10:40:44 GMT

We have newly setup a RH Linux and use vi to edit files , but sometimes it will be terminated and pop the below messages , what is the problem then ? thx

Vim: Caught deadly signal

Re: Edit file

RAC_1 — Fri, 26 Aug 2005 11:06:57 GMT

What is the signal name??

Re: Edit file

peterchu — Fri, 26 Aug 2005 11:31:35 GMT

"TERM"

is it the TERM settting problem ? thx

Re: Edit file

Raj D. — Fri, 26 Aug 2005 12:01:58 GMT

Hi peterchu ,

It seems that your terminal is not set properly , and vi is dropping.

Check with # echo $TERM

Also can do:
# set TERM=vt100
# export TERM
# vi test_file

Any luck,

Cheers ,
Raj.

Re: Edit file

Raj D. — Fri, 26 Aug 2005 12:03:33 GMT

Sorry it should be ,

(Hope you are using bash shell )
# TERM=VT220
# export TERM

Then try # vi test_file

Cheers,
Raj

Re: Edit file

Raj D. — Fri, 26 Aug 2005 12:06:29 GMT

Hi Peterchu ,

Also try with setting
# TERM=linux ; export TERM

Cheers,
Raj

Re: Edit file

Ivan Ferreira — Fri, 26 Aug 2005 14:11:50 GMT

I saw this on the Internet:

vim 5.3 is badly broken using TERM=linux. After starting it, if I hit
backspace once or twice quickly, it hangs in an infinite loop. Sending it a
signal from another shell prompt causes it to report:
Vim: Caught deadly signal TERM
Vim: Finished.
after which the shell is hosed (because vim didn't reset it when it exited).
Trying TERM=ansi works ok except that the function keys aren't defined.
TERM=xterm works for function keys 5-8, but not 1-4. I eventually made my
own terminal definition based on xterm which properly defines function keys
1-4, too. Could it be that I'm the only one using vim which has this
problem (I didn't see it in the archives)?

So, after you tried the TERM option, ensure that nobody with root privileges is issuing:

killall vi

Or sending kill to your vi process.