Bug 100771

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 
1.0.3705)

Description of problem:
This problem has been entered here before but none of the really explain the 
exact problem.

Problem: when installing vim-enhanced it creates a alias that profile runs and 
creates alias vi='vim'.  As you can see if you where to run vi it would in turn 
start vim.  This is great except when you loose your remote connection to the 
server or it receives a HANGUP or xterm gets closed when vim's runnign, etc.  
Basically anytime it's tty is lost.  If you where to run the actuall command 
vim this prolblem doesnt exist.  I beleive the reason for this is because maybe 
vim is detecting how it was started and is searching for it's process to kill?  
i dont know for sure.  all i know is the alias is whats causing this problem.  
VIM is not killing it self properly and in turn it consumes 99% CPU until it is 
killed.  This problem has been around for way too long now and is a big problem 
for my type of business (web hosting) as you can imagin many clients log in and 
use vi and alot of them may loose their session.

Here's a strace of what happens when the session is lost.

Version-Release number of selected component (if applicable):
6.1-18.7x.2

How reproducible:
Always

Steps to Reproduce:
1.log into the box via ssh
2.install vim-enhanced
3.ensure the alias vi='vim' exits
4.start vi by typeing vi bugtest
5.close the ssh session with out quiting vi
6.log back in, run top and wala, vim is going crazy

Additional info: