reminds me of the infamous xemacs "energizer bug", which was fixed in xemacs-21.4.10 I never encountered it in ViM, but on the other hand i'm using a self compiled ver. for HP-UX and Solaris and in Linux I have the Mandrake8.2 in work, and self-compiled (by gentoo) in home.
noam On Tue, 2003-02-04 at 13:49, Tzafrir Cohen wrote: > Hi > > The following bug has been created in vim in circa 6.0 . It has been fixed > in the Mandrake package of 6.1 , I believe (Mandrake 8.2?) , but I believe > that I still see it in the RedHat 8.0 package: > > If vim or gvim is killed abnormally (by SIGHUP, I think), it will not be > killed. Instead, it will get into a 100%cpu loop. > > (Redhat's bugzilla is currently unavailable for comments) > > Has this been fixed in the RH8.1 beta? > > -- > Tzafrir Cohen > mailto:[EMAIL PROTECTED] > http://www.technion.ac.il/~tzafrir > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > -- Noam Meltzer [EMAIL PROTECTED] ICQ: 4853872 ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
